Open travisperson opened 2 years ago
If we want to go crazy we could also add options to make including state and blockheaders optional as well, which would allow this method to be used to extract just the messages. However, ChainGetMessagesInTipset
already exists and can be used to grab this data and pack a car file manually.
With support of message receipts this will close out https://github.com/filecoin-project/lotus/issues/3849
This export should allow for exporting of CARv2 files with the index.
Checklist
Ideas
.Lotus component
Improvement Suggestion
The
ChainExport
command doesn't provide an accurate way to export a segment of the lotus chain.For archival and testing purposes it would be beneficial to be able to export an exact range of tipsets by adding a new method
ChainExportRange
that accepted twoTipSetKey
values as arguments and does not enforce a minimum epoch height between them (eg a call with both arguments the same should export a single TipSet).The
ChainExportRange
should also accept a set of optionsIt will be important to think through the exact inclusiveness of the method to ensure that no data is missed under the following usage:
I think ChainGetTipSetByHeight is the correct method to use here, I think as long as it's consistent it should be fine
The above should include the same data as
Additionally a command should be added to lotus-shed to support the usage of this API method, mostly because
chain export
enforces a minimum epochs to export.The export should construct CARv2 files with the index.