Preserve BLS and secp message identities in a Filecoin block export
A Lotus block export separates BLS messages from individually signed secp messages. An importer that assumes every entry has the same outer envelope can lose fields or misidentify a CID.
Inspect one physical block
Supply a real block CID. Read BlsMessages, SecpkMessages and the corresponding Cids list. BLS messages occur directly in their group, while a secp entry wraps a message and its signature.
{"jsonrpc":"2.0","id":1,"method":"Filecoin.ChainGetBlockMessages","params":[{"/":"<Filecoin block CID>"}]}
Keep group-specific decoding
Persist the signed envelope for a secp entry when its onchain identity matters. A CID recomputed from only its inner message identifies a different representation. Treat these as block inclusions. For executed messages across a whole parent tipset, use the dedicated parent-message and receipt APIs.
docs.filecoin.io ChainGetBlockMessages · docs.filecoin.io ChainGetParentMessages