Package and Supply Validations
To ensure the integrity of the Laika network, validators perform a critical check on the total Laika token supply:
L1 Supply Retrieval: Using the Bridge contract, validators obtain the total amount of Laika tokens currently locked in the designated Dogecoin bridge address on L1.
L2 Supply Retrieval: Validators query the Laika Token contract on L2 to retrieve the total supply of Laika tokens currently circulating on the L2 network.
Supply Comparison: Validators halt the chain if the L1 and L2 Laika token supplies don't match. This discrepancy could indicate a potential security breach or an error in the bridging process. If the supplies do not match, the block production is immediately stopped till the issue is resolved. This allows the chain to be always in spec and provide strict restrictions for the network to be functional.
Verifying Sequencer Packages
Validator software meticulously examines the data submitted by sequencers through sequencer packages. This verification process is critical for ensuring the integrity and validity of L2 transactions.
Transaction Validation: Validators confirm that the batched L2 transactions within the package are indeed valid and adhere to Laika's transaction format.
Data Availability Proof Verification: This step is crucial. Validators rigorously check the cryptographic proofs generated by sequencers. These proofs demonstrate that the corresponding L2 transaction data is demonstrably available on the L1 blockchain (Dogecoin).
Posting Validator Proofs: Based on the verified Sequencer package, each validator also creates their own ZK Proofs and submit them to the smart contract, this package is then later verified by other validators.
L1 and L2 Data Consistency Check
To ensure the integrity of the entire system, validators perform an additional critical check:
L1 Proof vs. L2 Contract Data: Validators compare the data availability proofs submitted by sequencers with the actual state of the Laika Token contract on L2. Any discrepancy between these data sources indicates a potential issue and could signify:
Malicious sequencer activity attempting to manipulate data.
Errors or inconsistencies between L1 and L2 states.
Last updated