L3
Pons L3
Transactions execute inside the Pons network with a dedicated sequencer and EVM-compatible state.
NETWORK
One layer for
the whole market.
Pons L3 is designed as an EVM-compatible Arbitrum Orbit chain above Robinhood Chain, bringing launch, liquidity, trading, and applications into one execution environment.
ExecutionArbitrum Nitro · proposed
ParentRobinhood Chain · 4663
SettlementEthereum
StatusDevelopment
NETWORK MODEL 01
Purpose-built execution,
standard underneath.
The chain is specialized around Pons without creating a proprietary contract environment. Developers keep EVM semantics while users get a network shaped around market activity.
RH
Robinhood Chain
Batches, bridge messages, and settlement commitments are posted to the parent environment.
Ξ
Ethereum
The parent chain ultimately inherits Ethereum settlement, placing Pons L3 inside the same layered security path.
ARCHITECTURE 02
Execution
The proposed network uses the Arbitrum Orbit / Nitro stack. Nitro provides EVM-equivalent execution, compressed transaction batches, and the same developer interfaces used across Ethereum tooling.
Contracts are written in Solidity and interact through standard JSON-RPC. Pons-specific launch and market contracts sit at the application layer rather than changing EVM behavior.
Sequencing
A primary sequencer orders transactions and returns fast soft confirmations. The launch configuration starts with an operator-managed sequencer, followed by redundancy, independent monitoring, and a documented outage procedure before mainnet.
A sequencer is operational infrastructure, not a security shortcut. Transaction batches and state commitments must still be published to the parent chain.
Settlement
Robinhood Chain is the proposed parent. Pons L3 contracts on Robinhood Chain receive assertions, bridge messages, and dispute-related state. Ethereum remains beneath Robinhood Chain as the final settlement layer.
Execution layerPons L3 Network
Parent chainRobinhood Chain
Parent chain ID
4663Settlement baseEthereum
Proof systemBoLD-compatible validation target
Bridge
The canonical bridge moves the native gas asset and supported tokens between Robinhood Chain and Pons L3. Deposits create retryable messages on the L3; withdrawals return through the Orbit outbox and their configured confirmation period.
The bridge interface will live at bridge.pons-l3.network. It remains unavailable until parent contracts and the rollup configuration are deployed.
Gas
Pons L3 can use ETH or a custom ERC-20 native gas token supported by Orbit. The final asset, address, fee collector, and conversion assumptions must be fixed before chain deployment because they affect bridging and node configuration.
No gas token is currently published. The website will not display a ticker or contract address until that choice is made on-chain.
Security model
Mainnet requires more than a running sequencer. The launch gate includes parent contracts, validator configuration, forced-inclusion paths, bridge verification, key separation, backups, monitoring, rate-limited public RPC, and an independently reproducible chain configuration.
- Sequencer and validator keys stay separate.
- Administrative contracts use a documented multisig and delay.
- Public RPC never exposes admin, personal, or debug namespaces.
- State, database, and configuration backups are tested before mainnet.
- Explorer and status services verify the chain independently.