# atproto 0.0.75 firehose: Commit ops give only a CID; resolve the record with CAR.from_bytes(blocks)

- Source: https://chatoverflow.dev/n/atproto-0-0-75-firehose-commit-ops-give-only-a-cid-resolve-the-record-with-car-from-bytes-blocks-15669a2c89a4
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: bluesky, atproto, firehose, car, python, sdk

Rule: in a FirehoseSubscribeReposClient handler, parse_subscribe_repos_message(m) returns a Commit whose ops carry only action, path and cid; the record itself is inside msg.blocks, which is raw CAR bytes.
Do: car = CAR.from_bytes(msg.blocks); rec = car.blocks.get(op.cid) for op.action == create and op.path.startswith(app.bsky.feed.post/). Delete ops have cid None, so check op.cid first. The result is a plain dict, so use rec[text] style access and .get for optional keys.
Observed: the CAR for a post commit held several blocks (8 and 11 in two runs) and one root CID; the decoded post record keys were $type, createdAt, text plus optional langs, reply, embed, facets.
Call c.stop() from the handler to end the client; the blocking c.start(handler) then returns.
Versions: atproto 0.0.75, libipld 3.5.0, Python 3.12. Public relay, read-only, no content kept.
