Kinto logoKinto

Kinto is an Orbit stack L2 with account abstraction and KYC enabled for all users, supporting both modern financial institutions and decentralized protocols.
Value Locked

$11.43 M


Canonically Bridged
$11.43 M
Externally Bridged
Natively Minted
  • Tokens
  • Daily TPS
  • 30D tx count
    9.22 K
  • Stage
    Stage 0
  • Type
    Optimistic Rollup
  • Purposes
    Universal, DeFi
  • ...




    Kinto Mainnet Genesis

    2023 Dec 15th

    Kinto mainnet is launched. Deposits by users are disabled.

    Learn more
    Risk summary
    Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.
    Risk analysis
    Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.
    Sequencer failureState validationData availabilityExit windowProposer failure

    State validation

    Fraud proofs (INT)

    No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks.

    Data availability

    On chain

    All of the data needed for proof construction is published on the base chain, which ultimately gets published on Ethereum.

    Exit window


    There is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.

    Sequencer failure

    Self sequence

    In the event of a sequencer failure, users can force transactions to be included in the project’s chain by sending them to L1. There is a 1d delay on this operation.

    Proposer failure

    Self propose

    Anyone can become a Proposer after 6d 8h of inactivity from the currently whitelisted Proposers.

    Rollup stage
    KintoKinto is a
    Stage 0
    Optimistic Rollup.
    There is no available node software that can reconstruct the state from L1 data, hence there is no way to verify that this system is a rollup.
    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.

    Fraud proofs ensure state correctness

    After some period of time, the published state root is assumed to be correct. For a certain time period, one of the whitelisted actors can submit a fraud proof that shows that the state was incorrect. The challenge protocol can be subject to delay attacks.

    • Funds can be stolen if none of the whitelisted verifiers checks the published state. Fraud proofs assume at least one honest and able validator (CRITICAL).

    1. How is fraud proven - Arbitrum documentation FAQ
    2. Arbitrum Glossary: Challenge Period
    3. RollupUser.sol - Etherscan source code, onlyValidator modifier
    4. Solutions to Delay Attacks on Rollups

    All transaction data is recorded on chain

    All executed transactions are submitted to an on chain smart contract. The execution of the rollup is based entirely on the submitted transactions, so anyone monitoring the contract can know the correct state of the rollup chain.

    1. Sequencing followed by deterministic execution - Arbitrum documentation
    2. SequencerInbox.sol - Etherscan source code, addSequencerL2BatchFromOrigin function

    The system has a centralized sequencer

    While proposing blocks 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.

    1. Sequencer - Arbitrum documentation

    Users can force any transaction

    Because the state of the system is based on transactions submitted on-chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract directly. Anyone can become a Proposer after approximately 6d 8h (45818 blocks) of inactivity from the currently whitelisted Proposers.

    1. SequencerInbox.sol - Etherscan source code, forceInclusion function
    2. Sequencer Isn’t Doing Its Job - Arbitrum documentation

    Regular exit

    The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is finalized the funds become available for withdrawal on L1. The process of block finalization usually takes several days to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.

    1. Transaction lifecycle - Arbitrum documentation
    2. L2 to L1 Messages - Arbitrum documentation
    3. Mainnet for everyone - Arbitrum Blog

    Tradeable Bridge Exit

    When a user initiates a regular withdrawal a third party verifying the chain can offer to buy this withdrawal by paying the user on L1. The user will get the funds immediately, however the third party has to wait for the block to be finalized. This is implemented as a first party functionality inside Arbitrum’s token bridge.

    1. Tradeable Bridge Exits - Arbitrum documentation

    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.

    Other considerations

    EVM compatible smart contracts are supported

    Arbitrum One uses Nitro technology that allows running fraud proofs by executing EVM code on top of WASM.

    • Funds can be lost if there are mistakes in the highly complex Nitro and WASM one-step prover implementation.

    1. Inside Arbitrum Nitro

    The system uses the following set of permissioned addresses:

    ProxyAdmin 0x74C7…00df

    Admin of UpgradeExecutor, RollupEventInbox, ChallengeManager, Outbox, L1ERC20Gateway, Bridge, L1GatewayRouter, Inbox.

    Validators/Proposers 0x64Cf…E04a

    They can submit new state roots and challenge state roots. Some of the operators perform their duties through special purpose smart contracts.

    Sequencers 0xe27f…6a39

    Central actors allowed to submit transaction batches to L1.

    ExecutorMultisig 0x17Eb…3B7d

    Multisig that can execute upgrades via the UpgradeExecutor. This is a Gnosis Safe with 3 / 4 threshold.

    Those are the participants of the ExecutorMultisig.

    BridgerOwnerMultisig 0xf152…5D82

    Multisig that can upgrade the Engen escrow. This is a Gnosis Safe with 3 / 6 threshold.

    Those are the participants of the BridgerOwnerMultisig.

    Bridger Sender Account 0x89A0…F82e

    EOA privileged to call bridgeDeposits() on the Bridger L1 escrow to send escrowed funds to the L2. It can also deposit tokens into the escrow itself by submitting signatures.

    Smart contracts

    The system consists of the following smart contracts:

    Main contract implementing Arbitrum One Rollup. Manages other Rollup components, list of Stakers and Validators. Entry point for Validators creating new Rollup Nodes (state commits) and Challengers submitting fraud proofs.

    Contract managing Inboxes and Outboxes. It escrows the native token used for gas on the chain. This contract stores the following tokens: ETH.

    Main entry point for the Sequencer submitting transaction batches.

    Entry point for users depositing ETH and sending L1 -> L2 messages.

    Contract that allows L2->L1 calls, i.e. messages initiated on L2 which eventually resolve in execution on L1.

    Contract allowed to upgrade the system.

    Contract that allows challenging invalid state roots. Can be called through the RollupProxy.

    OneStepProofEntry 0x0982…0662

    Contract used to perform the last step of a fraud proof.

    OneStepProverMemory 0x4811…A7f1

    Contract used to perform the last step of a fraud proof.

    OneStepProverMath 0x89AF…3e06

    Contract used to perform the last step of a fraud proof.

    OneStepProverHostIo 0x99a2…F878

    Contract used to perform the last step of a fraud proof.

    OneStepProver0 0xDf94…0622

    Contract used to perform the last step of a fraud proof.

    Router managing token <–> gateway mapping.

    Value Locked is calculated based on these smart contracts and tokens:

    Bridger escrow that swaps deposited assets to ‘L2 final assets’ that are later bridged to the L2 in batches.

    Main entry point for users depositing ERC20 tokens. Upon depositing, on L2 a generic, “wrapped” token will be minted.

    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).

    If you find something wrong on this page you can submit an issue or edit the information