Direct questions.
Direct answers.

The public EVM development network is live at rpc.pons-l3.network with chain ID 7333. The production Robinhood-settled Nitro network remains a separate deployment stage.

Pons L3 executes transactions in its own state environment and settles through Robinhood Chain, which is itself above Ethereum. A proxy to Robinhood RPC would not qualify.

The current architecture target is Arbitrum Orbit using Nitro and BoLD-compatible validation. The final configuration and exact versions will be published with the devnet manifest.

Not decided yet. Orbit supports ETH or a compatible ERC-20 native gas token. The decision affects bridge and node configuration and must be fixed before deployment.

Yes. The network targets standard Ethereum JSON-RPC and EVM behavior, so compatible wallets can add it using the published chain ID, RPC, currency, and explorer metadata.

No. Existing Robinhood Chain assets require canonical bridge representation or an explicit migration path. Token identity must never be inferred from a matching name or ticker.

The sequencer can return fast soft confirmations. Parent posting and final settlement happen later. The interface will distinguish these states rather than labeling everything simply “final.”

Users need a documented forced-inclusion path through the parent chain. Before mainnet, the project must test this path and publish the exact procedure.

No affiliation or endorsement is implied. Robinhood Chain is referenced as the intended parent environment.