Layer 2 blockchain · settles to Ethereum

Ronin ticker RON

No public-data lookups yet
4 reviewed developments
32 cited sources

Summary

Ethereum Layer 2 on the OP Stack since 12 May 2026; before that Ronin used a hand-picked validator set (2021) and then delegated proof of stake (April 2023). One sequencer, operated by Conduit, orders transactions into roughly 2-second blocks and streams preconfirmed partial blocks about every 250 ms. Batch data is posted to EigenDA and only commitments reach Ethereum. State roots are proposed to Ethereum through OP Stack dispute games: Boundless Kailua zero-knowledge fault proofs became the game used for withdrawals in early July 2026, but on 7 September 2026 withdrawals were switched back to a permissioned game that L2BEAT reports cannot resolve disputes for Ronin. RON pays gas; block production uses no stake or work of its own. 2 3 4 8 9 13 22 23

Design

System: Layer 2 blockchainRonin mainnet (chain ID 2020) ran its own validator set as an Ethereum sidechain until a hard fork at block 55,577,490 on 12 May 2026, when it migrated in place to an Ethereum Layer 2 built on the OP Stack, keeping its state, history and RON as the gas token. Transaction data goes to EigenDA with only commitments on Ethereum, so L2BEAT classes Ronin as an optimium and lists it outside its rollup categories because the proof system is not fully functional and there is no data-availability bridge. Pages that still call Ronin a Layer 1 are out of date.
Settles to: EthereumState roots, data commitments and the OP Stack bridge contracts live on Ethereum, while transaction data lives on EigenDA. Ronin's docs say blocks take about 12 minutes to finalize on Ethereum. L2BEAT reports that withdrawals through the OP Stack bridge wait at least a 3.5-day challenge period and 7 days after proving, but that bridge holds no user funds; user assets move through Chainlink CCIP instead.
Settlement family: Ethereum / EVM
Scarce resource: Other
State model: Accounts
Finality: Other
Who makes blocks: One sequencer run by Conduit, per Ronin's node documentation. L2BEAT lists one permissioned proposer address, a Conduit 4-of-11 multisig allowed to challenge or delete proposed state roots, and a 5-of-6 joint Ronin and Conduit multisig that can upgrade the Ethereum contracts with no delay. That joint multisig also holds the Guardian role, which can pause withdrawals and choose which dispute game withdrawals respect. Users can force transactions in through Ethereum with up to a 12-hour delay.
Fork choice: No open fork choice on the Layer 2: the canonical chain is derived from batch data on EigenDA referenced by commitments on Ethereum, and state roots settle through dispute-game contracts on Ethereum. L2BEAT notes that the data commitments are not checked against EigenDA on Ethereum, so the sequencer alone could post a commitment to unavailable data.

Qualifications

Scarce resource · Not applicable. Since May 2026 block production uses no stake or work of its own: the sequencer is operator-assigned. RON staking ended at the migration, and emissions now go to builders through Proof of Distribution, which is a reward program, not consensus.
Finality · Partial. Staged confidence: about 250 ms sequencer preconfirmations that can still be reorganized, about 2-second Layer 2 blocks, and about 12 minutes to finality on Ethereum per Ronin's docs. Withdrawal settlement depends on the proof system, which since 7 September 2026 relies on a permissioned proposer.
Ethereum security inheritance · Contested. Ronin says the chain now inherits Ethereum's security. L2BEAT reports data stored on EigenDA without an on-chain availability check, a proof system that cannot currently resolve disputes, and instantly upgradable contracts.
Data availability · Partial. Only data commitments are posted to Ethereum; the transaction data itself is held by EigenDA operators.
Pre migration history · Partial. Blocks before 12 May 2026 were produced by Ronin's former validator set (22 block producers under delegated proof of stake with about 6-second finality from October 2023) under different security assumptions.

Tradeoffs

This view follows one way of thinking about design priorities, often called the blockchain trilemma. The design-priorities lesson sets out the counter-view. Read the design-priorities lesson.

Emphasizes

Scalability Contested

Gives up

Decentralization and trust-minimized security: one operator sequences every transaction, only a permissioned proposer can post state roots, transaction data sits on EigenDA without an on-chain availability check, contracts can be upgraded instantly by a joint Ronin and Conduit multisig, and the validator staking that used to secure the chain was retired at the migration.Ronin's announcements say the chain now inherits Ethereum's security. L2BEAT's assessment (not even Stage 0, critical risks from the proof system, data availability and instant upgrades) contradicts that for now, so security is not listed as an emphasis. Ronin says it will eventually use zero-knowledge fraud proofs through Boundless Kailua. Because Ronin's own docs and posts describe the chain as inheriting Ethereum's security, this reading is marked contested.

Full node at home

Demanding 3 24 25Ronin's docs say there is no longer a separate Ronin node binary and point node operators to Conduit's Ronin repository (op-reth, op-node and an EigenDA proxy); that repository is now archived and redirects to Conduit's generic node repository. Conduit's archived Ronin guide lists 2 CPUs, 120 GiB memory and 800 GiB disk for mainnet; its current generic guide lists 4 to 8+ cores, 16 to 32 GB RAM and 500 GB to 1 TB+ NVMe, runs op-reth as an archive node, and restores snapshots from a requester-pays cloud bucket. A node also needs an Ethereum execution RPC and beacon endpoint.

Throughput claims

Theoretical peak: 1,000,000 tx/s 11Theoretical peak; not comparable across chains or with observed load.Stated in a September 2025 Ronin blog post as a benefit expected from adopting the OP Stack, before the migration.Not comparable: stated with no methodology, hardware, bandwidth or test setup published alongside it. Ignores propagation, state growth, data-availability cost and the single sequencer; not comparable with any other chain's figure. The same post promised 100 to 200 ms block times, while current docs describe about 2-second blocks with about 250 ms preconfirmations. Home-node incompatibility is an inference from the published node resource specifications, not a measured result.
Observed window: 1.54 22Observed in the stated window only; not capacity.User operations per second as counted by L2BEAT (UOPS), not raw transactions.Past-day figure displayed on L2BEAT's Ronin page when retrieved on 2026-09-27.Measures demand during one day, not capacity. A third-party count that changes daily; re-check before quoting.

Headline figures are not comparable across chains. A theoretical peak is never a like-for-like number.

Scaling layers

No scaling layer recorded in this profile.

Capabilities

Capabilities of Ronin: how each one is provided, or its research status
Capability	How it is provided	Notes and sources
Account abstraction	Structured assessment pending	Not yet assessed for any chain.
Atomic swaps	Unknown	A protocol-level trust-minimized swap mechanism on Ronin was not reviewed; EVM contracts could implement one but none was verified.
Authenticated data publication	Unknown	Not yet assessed under this row's current definition.
Light clients	Unknown	A light-client verification path for Ronin was not reviewed.
Native staking or delegation	Structured assessment pending	Not yet assessed for any chain.
On-chain governance	Structured assessment pending	Not yet assessed for any chain.
Parallel execution	Structured assessment pending	Not yet assessed for any chain.
Payment or state channels	Unknown	No payment or state channel layer anchored to Ronin was reviewed.
Programmable spending	Native (protocol or core-team software) Earlier definition	Ronin runs EVM smart contracts, so spend conditions are contracts. A January 2025 Ronin support article describes the transition from a permissioned network to one where developers can deploy applications without prior approval. 5 19 22
Protocol-verified messaging	Structured assessment pending	Not yet assessed for any chain.
Reversible transfers or recovery	Unknown	Not yet assessed under this row's current definition.
Rollups	Unknown	Absence was not verified, so the rule that absence needs a source makes this cell unknown. Earlier finding: Ronin announced in June 2024 that builders could launch zero-knowledge chains on top of Ronin with Polygon's development kit, and in August 2025 said those plans would be re-evaluated; no live rollup anchored to Ronin was found. Ronin itself is an Ethereum Layer 2. 10 15
Shielded transfers	Structured assessment pending	Not yet assessed for any chain.
Signed partial offers	Unknown	Not yet assessed under this row's current definition.

Reading these values

How this feature is provided: Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
Structured assessment pending: The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
Unknown: The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
Earlier definition: Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
Reading across rows: The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.

Definitions, schema version and review history

Ecosystem & custody

Ecosystem products for Ronin
Product type	Status	Notes and sources
Automated market makers	First-partyKatana	Ronin's docs describe Katana as a decentralized exchange for trading tokens within the Ronin ecosystem: an automated market maker with V2 pools and V3 concentrated-liquidity pools, reached through the Ronin app. Ronin said the migration did not affect Katana pools, and its September 2026 governance proposal concerns Katana RON pools. Liquidity depth was not measured and other venues were not reviewed. 6 8 12 As of Sep 27, 2026.
Issuer-native stablecoins	ThinPHPC (Coins.ph)	Ronin reports that Coins.ph launched PHPC, a Philippine peso stablecoin, on Ronin in July 2024. Coins.ph's own PHPC whitepaper names itself as issuer, says PHPC will also be issued on Ronin, and labels PHPC as operating under the Philippine central bank's regulatory sandbox, with holders reimbursed when that period ends. Current PHPC circulation on Ronin was not measured. Circle's USDC address list and Tether's supported-protocol list do not include Ronin, so USDC on Ronin is a representation bridged through Chainlink CCIP, not issuer-native. 16 17 18 27 28 32 As of Sep 27, 2026.
Algorithmic stablecoins	Unknown	Algorithmic or hybrid stablecoins on Ronin were not reviewed. As of Sep 27, 2026.
Bridges	First-partyRonin Bridge app (Chainlink CCIP), OP Stack standard bridge contracts, Legacy Ronin Bridge (deprecated)	Ronin's validators chose Chainlink CCIP as the canonical bridge in 2024 and moved all legacy bridge funds to it in April 2025. Chainlink's directory lists Ronin lanes to Ethereum and Base. The May 2026 migration deployed the OP Stack bridge, but L2BEAT reports it holds no user funds. Third-party bridges were not reviewed. Risk: CCIP transfers depend on Chainlink's oracle networks, its risk management network and token-pool rate limits, not on Ethereum's dispute games. The legacy gateway still holds residual balances released by a stake-weighted operator multisig, and some Ronin bridge docs still describe that older design. The OP Stack bridge contracts can be upgraded with no delay. 7 16 22 26 As of Sep 27, 2026.
Block explorers	First-partyRonin Explorer (explorer.roninchain.com, Blockscout-based), Blockscout (ronin.blockscout.com)	Ronin's May 2026 post introduced a new explorer at explorer.roninchain.com, which runs Blockscout, and said the legacy explorer in the Ronin app was retired; some Ronin docs pages still link the old address. Explorer indexes are not canonical consensus. 8 29 30 As of Sep 27, 2026.
Hardware wallets	ThinLedger through Ronin Wallet, Trezor through MetaMask, Rabby or Ronin Wallet	See custody rows: Trezor's Ronin page names only third-party wallet apps, and no Ledger page naming Ronin was found; both devices sign through third-party or Ronin wallet software, the Ledger with its Ethereum app. 20 21 31 As of Sep 27, 2026.

Hardware-wallet custody

Hardware-wallet custody for Ronin
Device maker	Status	What users can and cannot do
Ledger	Through an intermediaryRonin Wallet browser extension or mobile app, signing with Ledger's Ethereum appSame as native: Unknown	Can: Import a Ledger account into Ronin Wallet and approve Ronin transactions on the device with Ledger's Ethereum app open Cannot: Manage Ronin accounts in Ledger's own app, as far as this review found Cannot: Use the Ledger with the Ronin Wallet extension in Firefox, per Ronin's support articleLedger's Ronin coin page returned 404 and no Ledger page naming Ronin was found. Ronin's support article dates from August 2024, before the Layer 2 migration; that the same flow still works was not re-tested. 20 As of Sep 27, 2026.
Trezor	Through an intermediaryMetaMask or Rabby (named on Trezor's Ronin page) or the Ronin Wallet extension (named by Ronin support)Same as native: Unknown	Can: Hold and send RON on the Ronin network with a Trezor Safe 3, 5 or 7 connected to MetaMask or Rabby Can: Import a Trezor account into the Ronin Wallet extension Cannot: Manage Ronin in Trezor's own Suite app; Trezor's page names only third-party wallet appsTrezor's Ronin page still describes RON as a token that will eventually pay gas and secure the network, so its text predates current Ronin; transactions are still approved on the device, but parity with assets that Trezor Suite supports directly was not assessed. 21 31 As of Sep 27, 2026.

Public data

iKnow Blockchain has no public-data lookups for Ronin yet. This is a limit of the service, not a statement about the network.

Public-data lookups for Ronin
Lookup	Status	What it covers and its limits
Address or account	Not available yet	Public-data lookups for this chain are not built yet.
Tokens and assets	Not available yet	Public-data lookups for this chain are not built yet.
NFTs	Not available yet	Public-data lookups for this chain are not built yet.
Transactions	Not available yet	Public-data lookups for this chain are not built yet.

A lookup covers one address or transaction from one provider. It is never a complete wallet, and an error or private value is reported as unknown, not zero. About public data · Connect your AI

Sourced developments

Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.

Publication date · newest first

Published Sep 22, 2026FoundationProposed, not adopted

Ronin announced RON-holder governance and its first proposal

Ronin announced a governance framework in which RON holders vote on economic and treasury matters, with RGP-1, a proposal to deploy treasury assets as Katana liquidity for RON pairs, expected to start in October 2026. It also scheduled a first transfer of 16,234,252 RON from former staking rewards to the treasury in October.
- Proposal:announced; vote expected October 2026
- Implementation:not started
- Release:not released
- Activation:not active as of this review
Date basis: Ronin blog post publication date: 2026-09-22.

Source: Ronin blog — Ronin Governance (external site)
Published Sep 7, 2026ProtocolVerified against sources

Ronin withdrawals switched back from Kailua ZK proofs to a permissioned game

An Ethereum transaction on 7 September 2026 set Ronin's withdrawal contracts back to the permissioned dispute game, about two months after Boundless Kailua zero-knowledge proofs were enabled in early July 2026 (L2BEAT links a transaction dated 1 July). L2BEAT reports that the permissioned game's proof program cannot execute Ronin's state, so security now rests on the permissioned proposer.
- Implementation:executed on Ethereum
- Release:mainnet contracts
- Activation:permissioned game active since 2026-09-07; reason not published in reviewed sources
Date basis: Ethereum block timestamp of the linked transaction (2026-09-07 10:31 UTC) and L2BEAT's milestone date; no Ronin announcement was found.

Sources: Etherscan — Ethereum transaction switching Ronin withdrawals to the permissioned game (external site) · Etherscan — Ethereum transaction enabling Kailua proofs for Ronin (external site) · L2BEAT — Ronin (external site)
Published May 13, 2026ProtocolVerified against sources

Ronin mainnet became an Ethereum Layer 2 on the OP Stack

After a planned outage of about 10 hours on 12 May 2026, Ronin mainnet resumed as an OP Stack Layer 2 run by Conduit, with data on EigenDA and RON kept as gas. Validator staking ended, emissions fell to 5 million RON a year for builders, and a new explorer replaced the old one.
- Proposal:OP Stack adoption voted by governing validators in 2025
- Implementation:Completed
- Release:Mainnet
- Activation:active since 12 May 2026
Date basis: Ronin blog post publication date: 2026-05-13; the hard fork was scheduled for 12 May 2026 at block 55,577,490 per Ronin's 22 April 2026 post.

Sources: Ronin blog — Ronin is Home. (external site) · Ronin blog — Ronin is coming home to Ethereum (external site) · Ronin blog — Powering Ronin's Homecoming to Ethereum (external site) · L2BEAT — Ronin (external site)
Published Feb 6, 2026ProtocolVerified against sources

Ronin's Saigon testnet completed its move to the OP Stack

Ronin announced that its Saigon testnet had migrated to an OP Stack Layer 2 with Optimism and Conduit, as a rehearsal for mainnet, and told node operators to switch to reth and op-node.
- Proposal:OP Stack adoption voted by governing validators in 2025
- Implementation:completed on testnet
- Release:testnet only
- Activation:active on Saigon testnet
Date basis: Ronin blog post publication date: 2026-02-06.

Sources: Ronin blog — The Saigon Testnet Migration is Complete (external site) · Ronin blog — Powering Ronin's Homecoming to Ethereum (external site)

Topics your AI can explain

Your AI can explain these topics for Ronin through the connection, with sources.

What Ronin is today
How Ronin orders blocks and what secures them
Accounts and addresses on Ronin
RON, gas and fee units on Ronin
When a Ronin transaction is final
Bridging to Ronin and holding RON
Proof of Distribution, the treasury and RON governance

Known gaps

What this profile's review did not establish:

Ronin has not published an explanation, found in this review, for the 7 September 2026 switch of withdrawals back to the permissioned dispute game, or a date for re-enabling zero-knowledge fault proofs.
Who controls the joint Ronin and Conduit upgrade multisig, and how the September 2026 statement that protocol decisions remain under validator governance maps to those keys, was not established.
The legal and corporate operator arrangement between Sky Mavis and Conduit for the sequencer was not sourced beyond Ronin's statement that Conduit operates the Layer 2 infrastructure.
L2BEAT notes that Ronin's Superchain configuration contract is a local fork rather than the shared Optimism Superchain contract; whether Ronin is otherwise a member of the Optimism Superchain was not confirmed.
The current fee formula (execution fee, any Ethereum data component, minimum gas price) after the migration is not documented in the reviewed Ronin docs; the EIP-1559 page describes the earlier validator chain.
Current full-node disk size and bandwidth needs were not measured; the node posture relies on Conduit's published resource specifications.
Ledger support was not verified on a Ledger page (Ronin coin page 404; the supported-asset list did not render); the Ledger and Trezor flows come from Ronin support articles written before the migration.
Coins.ph's whitepaper confirms PHPC issuance on Ronin under the central bank's sandbox, but whether the sandbox period is still running and how much PHPC circulates on Ronin today were not confirmed.
Ronin's bridge history, including past security incidents, was not re-sourced in this review.
Trust-minimized swaps, reversible-transfer or account-recovery features, light-client verification, channels and algorithmic stablecoins on Ronin were not reviewed.
Some Ronin docs pages (tokenomics, Ronin Bridge, explorer link) still describe the pre-migration chain and conflict with the May 2026 announcements.

Sources

Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.

All 32 sources were checked in the last 30 days.

Introduction to Ronin (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Network information (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Run a node (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Flashblocks (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Smart contract guidelines (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Katana (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
CCIP Bridge (external site)Ronin (Sky Mavis) · retrieved Sep 27, 2026
Ronin is Home. (external site)Ronin blog · retrieved Sep 27, 2026
Ronin is coming home to Ethereum (external site)Ronin blog · retrieved Sep 27, 2026
Ronin's Homecoming to Ethereum (external site)Ronin blog · retrieved Sep 27, 2026
Powering Ronin's Homecoming to Ethereum (external site)Ronin blog · retrieved Sep 27, 2026
Ronin Governance (external site)Ronin blog · retrieved Sep 27, 2026
Decentralization on Ronin (external site)Ronin blog · retrieved Sep 27, 2026
Introducing Fast Finality on Ronin (external site)Ronin blog · retrieved Sep 27, 2026
Introducing Ronin zkEVM (external site)Ronin blog · retrieved Sep 27, 2026
The Ronin Bridge Chainlink CCIP migration is complete (external site)Ronin blog · retrieved Sep 27, 2026
PHPC is live on Ronin (external site)Ronin blog · retrieved Sep 27, 2026
Ronin and QRPH join forces (external site)Ronin blog · retrieved Sep 27, 2026
Understanding the Differences Between Permissioned and Permissionless Networks (external site)Ronin Support · retrieved Sep 27, 2026
Setting Up Your Ledger Wallet (external site)Ronin Support · retrieved Sep 27, 2026
Setting Up Your Trezor Wallet (external site)Ronin Support · retrieved Sep 27, 2026
Ronin (external site)L2BEAT · retrieved Sep 27, 2026
Ethereum transaction switching Ronin withdrawals to the permissioned dispute game (external site)Etherscan · retrieved Sep 27, 2026
conduitxyz/ronin-migration-reth-docker (archived) (external site)Conduit · retrieved Sep 27, 2026
conduitxyz/conduit-optimism-external-node (external site)Conduit · retrieved Sep 27, 2026
Ronin CCIP Network - Mainnet Cross-Chain Configuration (external site)Chainlink · retrieved Sep 27, 2026
USDC contract addresses (external site)Circle · retrieved Sep 27, 2026
Supported protocols (external site)Tether · retrieved Sep 27, 2026
Ronin Mainnet blockchain explorer (external site)Ronin (Blockscout) · retrieved Sep 27, 2026
Ronin blockchain explorer (external site)Blockscout · retrieved Sep 27, 2026
Ronin wallet (external site)Trezor · retrieved Sep 27, 2026
PHPC Whitepaper (external site)Coins.ph · retrieved Sep 27, 2026

Report an error

Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.

Report an error about Ronin Corrections log

Funding disclosure

Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding