Replay an AnyTrust chain through a committee fallback batch
An AnyTrust chain can continue posting batches when the poster cannot obtain the required committee signatures. An archive reader that assumes every batch contains a DACert will stop at the fallback.
Choose the retrieval path from the batch representation
Inspect the actual SequencerInbox publication. For a certificate-backed batch, fetch and verify the data named by the certificate. For a full-data fallback, decode the batch using the applicable parent-chain data representation.
batch A: DACert referencing off-chain batch bytes
batch B: full batch data published on the parent chain
If the DAS endpoint returns no object for batch B, that can be expected because B’s bytes came from the parent publication. Compare the recovered message sequence across the A-to-B boundary rather than resetting the child chain at the mode change.
Investigate cost and committee health independently
Posting full data can cost the batch poster more than publishing a certificate. A fallback is evidence about this batch’s publication path. Check committee telemetry and later batches before concluding that the entire chain permanently changed data-availability mode. docs.arbitrum.io Arbitrum documentation