Reorg Protection (Dynamic Lane Management System)
A guide to the Dynamic Lane Management System
A guide to how the DLMS uses volume and risk metrics to assign the correct reorg-protection lane for each batch.
Blockchain Types and Reorg Risk Profiles
ASMS Dynamic Lane Management System
Our Application Specific Multichain Sequencer (ASMS) introduces a novel dynamic lane management mechanism that can be tailored to different needs for different applications to mitigate against long-tail risk introduced to applications running over multiple execution environments. There are multiple implementation mechanisms which carry different development and maintenance overheads for teams building with ASMS.
At its heart the ASMS uses a volume based lane management system that looks at aggregated volume originating from a source chain against global volume or global liquidity depending on the use-cases. The volume based lane management system is an additional security measure as malicious actors would not be able to split transactions to be undetected and it significantly increases the attack costs as an attacker would need to compromise multiple systems in addition to the ASMS, such as the underlying security architecture of the underlying chains (33% attack against Ethereum consensus, Optimism Fault Dispute Game, Zero-Knowledge proof systems etc.).
On-Chain Volume Verification
A key component is the volume_flow.sol contract deployed on each chain is a key component that tracks and limits the verifications based on volume over a set period of time.
They contracts can also be engineered to hardcode required verification for set volume, the following table depicts an example. Its key to tailor and set it based on the acceptable risk parameters for the specific application:
<1%
L2 finality with 8 block confirmations
<5%
L1 inclusion
>5%
L1 finality
Sequencer Dynamic Lane Management
The Multichian Sequencer can dynamically move transactions between the different lanes as they open up (e.g. as it drops below the maximum volume). This can potentially have additional costs, as they might require regenerating proofs. The goal of this system is to minimize latency for applications.
Proof-based protections
Different lanes can require different verification levels, by building different type of proofs. Depending on the on-chain conditions incorrect verification levels will result in a failed transactions, providing even more robust security.
Last updated