Capx Chain, utilizing the Arbitrum Nitro stack, achieves consensus through an optimistic rollup mechanism. This means L2 (Capx Chain) transactions are executed and batched with the optimistic assumption of validity for speed and low cost. True finality and security are derived from the underlying L1 (Ethereum) through a system of state assertions and fraud proofs.
Capx Chain Consensus Flow
(L2: Capx Chain Execution & Proposal)
User ---sends L2 Tx---> [Capx Chain Sequencer]
[Sequencer]
[Transaction Batch]
and a new [L2 State Root_S]
.---Soft Confirmation---> User
.[Sequencer] ---submits Tx Batch (calldata)---> [L1 Ethereum: Inbox Contract]
(L1: Assertion & Challenge Period)
[Asserter (e.g., Sequencer)] ---posts Assertion(L2 State Root_S)---> [L1 Ethereum: Rollup Core Contract]
[Rollup Core Contract] ---initiates Challenge Period (e.g., 7 days)---
(L2 & L1: Validation & Potential Challenge)
[Capx Chain Validators (L2 Full Nodes)]
:
[Transaction Batch]
from L1 Inbox.[L2 State Root_V]
.[L2 State Root_V]
with asserted [L2 State Root_S]
on L1.Decision Point during Challenge Period:
State Root_V == State Root_S
(Happy Path):
IF Challenge Period Ends without successful challenge:
[L1 Ethereum: Rollup Core Contract] ---confirms Assertion---> [L2 State Root_S is Finalized]
✅State Root_V != State Root_S
(Dispute Path):
[A Challenging Validator] ---initiates Fraud Proof against Assertion(L2 State Root_S)---> [L1 Ethereum: Rollup Core Contract]
OneStepProof
mechanism) to determine the correct state transition.IF Challenger Wins:
Fraudulent assertion is rejected, Challenger is rewarded, Asserter is penalized. The correct state can be asserted.IF Asserter Wins:
Challenge is dismissed, Challenger may lose their stake. Assertion proceeds towards finalization.Sequencer (L2):
calldata
to an Inbox
contract on Ethereum L1. This ensures data availability.Asserters (Typically includes the Sequencer, can be other permissioned L2 Nodes):
Rollup Core
contract on Ethereum L1. This is an “assertion” about the outcome of executing a specific batch of L2 transactions.Validators (Full L2 Nodes):
Inbox
. They compute their own version of the L2 state root.Ethereum L1 Contracts (e.g., Rollup Core
, Inbox
, Bridge
):
Inbox
: Receives transaction data from the Sequencer.Rollup Core
: Manages the state of the rollup, tracks assertions, and facilitates the fraud proof mechanism.Capx Chain, utilizing the Arbitrum Nitro stack, achieves consensus through an optimistic rollup mechanism. This means L2 (Capx Chain) transactions are executed and batched with the optimistic assumption of validity for speed and low cost. True finality and security are derived from the underlying L1 (Ethereum) through a system of state assertions and fraud proofs.
Capx Chain Consensus Flow
(L2: Capx Chain Execution & Proposal)
User ---sends L2 Tx---> [Capx Chain Sequencer]
[Sequencer]
[Transaction Batch]
and a new [L2 State Root_S]
.---Soft Confirmation---> User
.[Sequencer] ---submits Tx Batch (calldata)---> [L1 Ethereum: Inbox Contract]
(L1: Assertion & Challenge Period)
[Asserter (e.g., Sequencer)] ---posts Assertion(L2 State Root_S)---> [L1 Ethereum: Rollup Core Contract]
[Rollup Core Contract] ---initiates Challenge Period (e.g., 7 days)---
(L2 & L1: Validation & Potential Challenge)
[Capx Chain Validators (L2 Full Nodes)]
:
[Transaction Batch]
from L1 Inbox.[L2 State Root_V]
.[L2 State Root_V]
with asserted [L2 State Root_S]
on L1.Decision Point during Challenge Period:
State Root_V == State Root_S
(Happy Path):
IF Challenge Period Ends without successful challenge:
[L1 Ethereum: Rollup Core Contract] ---confirms Assertion---> [L2 State Root_S is Finalized]
✅State Root_V != State Root_S
(Dispute Path):
[A Challenging Validator] ---initiates Fraud Proof against Assertion(L2 State Root_S)---> [L1 Ethereum: Rollup Core Contract]
OneStepProof
mechanism) to determine the correct state transition.IF Challenger Wins:
Fraudulent assertion is rejected, Challenger is rewarded, Asserter is penalized. The correct state can be asserted.IF Asserter Wins:
Challenge is dismissed, Challenger may lose their stake. Assertion proceeds towards finalization.Sequencer (L2):
calldata
to an Inbox
contract on Ethereum L1. This ensures data availability.Asserters (Typically includes the Sequencer, can be other permissioned L2 Nodes):
Rollup Core
contract on Ethereum L1. This is an “assertion” about the outcome of executing a specific batch of L2 transactions.Validators (Full L2 Nodes):
Inbox
. They compute their own version of the L2 state root.Ethereum L1 Contracts (e.g., Rollup Core
, Inbox
, Bridge
):
Inbox
: Receives transaction data from the Sequencer.Rollup Core
: Manages the state of the rollup, tracks assertions, and facilitates the fraud proof mechanism.