Posting on the Blockchain
Last updated
Last updated
Once the transactions are organized and secured through the sequencer and Merkle Tree, the next step is to post them on the blockchain for transparency and verification. At the same time, the system groups these transactions into epochs, which are time-based windows for processing transactions.
In the decentralized method (Submission B), orders are posted directly on the blockchain.
Orders that went through the sequencer (Submission A) also end up on the blockchain once they are fully processed by the sequencer.
Transactions secured with the Merkle Tree Root are collected and grouped into epochs, which are blocks of time (10 seconds long). All the transactions made within that time period are added together and processed as one group.
Think of an epoch like a time bucket (every 10 seconds), where the blockchain collects all the transactions during that time and puts them into one block. This helps the system handle lots of transactions efficiently while keeping everything organized.
Once the transactions are bundled, they are posted on the blockchain. This step makes the entire batch of transactions visible to everyone, ensuring full transparency.
Because the blockchain is decentralized, Node Validators can check transactions without relying on a central authority. They ensure that transactions match the user submission order, verify that they are processed in the correct order, and compare on-chain (Submission B) data with the off-chain (Submission A) data received from the sequencer. This means Node Validators check if the off-chain (sequencer-processed) and on-chain versions of the transaction are aligned, guaranteeing the integrity of the system, and confirming that all transactions are fairly handled and visible to everyone.