RARI Chain
Badges
About
RARI Chain embeds royalties on the node level to guarantee royalty payments. A secure, low-cost, decentralized Ethereum L3 blockchain powered by Arbitrum.
Badges
About
RARI Chain embeds royalties on the node level to guarantee royalty payments. A secure, low-cost, decentralized Ethereum L3 blockchain powered by Arbitrum.
Recategorisation
The project will be classified as "Other" due to its specific risks that set it apart from the standard classifications.
The project will move to Others because:
Consequence: projects without a sufficiently decentralized set of challengers rely on few entities to safely update the state. A small set of challengers can collude with the proposer to finalize an invalid state, which can cause loss of funds.
Consequence: projects without a data availability bridge fully rely on single entities (the sequencer) to honestly rely available data roots on Ethereum. A malicious sequencer can collude with the proposer to finalize an unavailable state, which can cause loss of funds.
2024 May 09 — 2025 May 09
2024 May 10 — 2025 May 09
RARI disables proof system
2025 May 5th
The proof system and reference to Blobstream are disabled.
RARI integrates Espresso sequencer
2025 Jan 30th
RARI is the first chain to integrate Espresso TEE sequencer.
Arbitrum OneFunds can be stolen if
Funds can be lost if
MEV can be extracted if
| SEQUENCER FAILURE | STATE VALIDATION | DATA AVAILABILITY | EXIT WINDOW | PROPOSER FAILURE | |
| Arbitrum One L2 | Self sequence | Fraud proofs (INT) | Onchain | 10d | Self propose |
| RARI Chain L3 • Individual | Self sequence | None | External | None | Self propose |
| RARI Chain L3 • Combined | Self sequence | None | External | None | Self propose |
Currently the system permits invalid state roots. More details in project overview.
Proof construction and state derivation fully rely on data that is posted on Celestia. Sequencer tx roots are not checked against the Blobstream bridge data roots onchain, but L2 nodes can verify data availability by running a Celestia light client.
There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Anyone can become a Proposer after 12d 17h of inactivity from the currently whitelisted Proposers.
Data is posted to Celestia
Transactions roots are posted onchain and the full data is posted on Celestia. Since the Blobstream bridge is not used, availability of the data is not verified against Celestia validators, meaning that the Sequencer can single-handedly publish unavailable roots.
Funds can be lost if the sequencer posts an unavailable transaction root (CRITICAL).
Funds can be lost if the data is not available on the external provider (CRITICAL).
The information in the section might be incomplete or outdated.
The L2BEAT Team is working to research & validate the content before publishing.
Arbitrum OneThe system has a centralized sequencer
While forcing transaction is open to anyone the system employs a privileged sequencer that has priority for submitting transaction batches and ordering transactions.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
Users can force any transaction
Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly. After a delay of 1d in which a Sequencer has failed to include a transaction that was directly posted to the smart contract, it can be forcefully included by anyone on the host chain, which finalizes its ordering.
Espresso TEE sequencer
Rari integrates with Espresso sequencing. In addition to providing regular pre-confirmations, the sequencer publishes blocks to the Espresso Network. The integration expects the transaction batch poster to run inside a Trusted Execution Environment (TEE), and it is programmed to verify batch inclusion in a Espresso Network block before publishing it to the host chain. However, the confirmations provided by Espresso Network are additive, and the batch poster can skip Espresso inclusion checks should the Espresso Network be down or unavailable. To ensure the batch poster is running inside a TEE, the sequencer inbox contract on the host chain was updated so that the data posting function also includes a TEE attestation as input, a “quote”, that is verified onchain by the EspressoTEEVerifier for each batch transaction. The verifier checks the quote signature originates from inside the TEE and reverts if unsuccessful.
Withdrawals can be delayed if the owner of EspressoTEEVerifier updates the contract verification values (mrEnclave, mrSigner) and it is no longer possible to verify the TEE quote.
Arbitrum OneRegular messaging
Autonomous exit
Users can (eventually) exit the system by pushing the transaction on L1 and providing the corresponding state root. The only way to prevent such withdrawal is via an upgrade.
EVM compatible smart contracts are supported
Arbitrum One uses Nitro technology that allows running fraud proofs by executing EVM code on top of WASM.
Arbitrum One
Roles:
Can submit transaction batches or commitments to the SequencerInbox contract on the host chain.
Can propose new state roots (called nodes) and challenge state roots on the host chain.
Actors:
- A Multisig with 3/4 threshold.
- Can act on behalf of UpgradeExecutor.
- Is allowed to interact with RollupProxy - Pause and unpause and set important roles and parameters in the system contracts: Can delegate Sequencer management to a BatchPosterManager address, manage data availability, DACs and the fastConfirmer role, set the Sequencer-only window, introduce an allowList to the bridge and whitelist Inboxes/Outboxes - acting via UpgradeExecutor.
- Can upgrade the implementation of UpgradeExecutor, Bridge, GatewayRouter, Inbox, RollupEventInbox, ERC20Gateway, CustomGateway, Outbox, SequencerInbox, ChallengeManager - acting via ProxyAdmin, UpgradeExecutor.
- Can upgrade the implementation of RollupProxy - acting via UpgradeExecutor.
Used in:
- Is allowed to interact with SequencerInbox - Add/remove batchPosters (Sequencers).
- A Sequencer - Can submit transaction batches or commitments to the SequencerInbox contract on the host chain.
Arbitrum One
Central contract for the project’s configuration like its execution logic hash (wasmModuleRoot) and addresses of the other system contracts. Entry point for Proposers creating new Rollup Nodes (state commitments) and Challengers submitting fraud proofs (In the Orbit stack, these two roles are both held by the Validators).
The Espresso TEE sequencer (registered in this contract) can submit transaction batches or commitments here. This version of the SequencerInbox also supports commitments to data that is posted to Celestia.
Contract that allows challenging state roots. Can be called through the RollupProxy by Validators or the UpgradeExecutor.
- Central contract defining the access control permissions for upgrading the system contract implementations.
- Can act on behalf of ProxyAdmin.
- Can be used to interact with RollupProxy - Pause and unpause and set important roles and parameters in the system contracts: Can delegate Sequencer management to a BatchPosterManager address, manage data availability, DACs and the fastConfirmer role, set the Sequencer-only window, introduce an allowList to the bridge and whitelist Inboxes/Outboxes.
- Can be used to upgrade implementation of RollupProxy.
Implementation used in:
Escrows deposited ERC-20 assets for the canonical Bridge. Upon depositing, a generic token representation will be minted at the destination. Withdrawals are initiated by the Outbox contract. This contract can store any token.
This routing contract maps tokens to the correct escrow (gateway) to be then bridged with canonical messaging.
Escrows deposited assets for the canonical bridge that are externally governed or need custom token contracts with e.g. minting rights or upgradeability. This contract can store any token.
Can be used to upgrade implementation of UpgradeExecutor, Bridge, GatewayRouter, Inbox, RollupEventInbox, ERC20Gateway, CustomGateway, Outbox, SequencerInbox, ChallengeManager.
One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.
Helper contract sending configuration data over the bridge during the systems initialization.
One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.
The QuoteVerifier contract is used by the EspressoTEEVerifier to verify the validity of the TEE quote.
One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.
This contract implements view only utilities for validators.
Proxy used in:
The Espresso TEE verifier is used by the SequencerInbox contract to verify the batch attestations signed by the TEE.
One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.
Value Secured is calculated based on these smart contracts and tokens:
Main entry point for users depositing ERC20 tokens. Upon depositing, on L2 a generic, “wrapped” token will be minted.
Main entry point for users depositing ERC20 tokens that require minting custom token on L2.
Contract managing Inboxes and Outboxes. It escrows ETH sent to L2.
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).