BatchInbox

Deployed on L1, used to receive batch transaction information sent by the L2 Sequencer.

A transaction is submitted by a batcher to a data availability provider to ensure channels are accessible. These transactions contain one or more complete frames, which may pertain to different channels. A channel's frame might be divided among multiple batcher transactions.

When submitting to TON calldata, the batcher transaction's receiver must be the sequencer inbox address. Additionally, the transaction must be signed by an authorized batch submitter account recognized within the network.

In this part, we drew inspiration from the concepts of inscription and op-batcher. By leveraging messages to store transaction batches, we ensure that the transaction data remains traceable and queryable. This approach not only enhances the transparency and accountability of the transactions but also facilitates easier auditing and verification of the transaction history.

By adopting this methodology, we aim to create a more robust and reliable cross-chain transaction system, where every transaction can be efficiently tracked and analyzed. This is crucial for maintaining the integrity of the system and providing users with the confidence that their transactions are secure and verifiable.