Veilify uses two network layers: Veilify Network is the virtual network your wallet uses for private actions; Robinhood Chain is the settlement blockchain where the pool contracts run. Solana is planned as a second settlement chain. These names describe different roles.

​
Veilify Network: wallet and privacy RPC

Veilify Network is designed to accept wallet-signed transactions through the Veilify RPC proxy and turn supported actions into proof-backed pool operations. It does not produce its own blocks. It settles on Robinhood Chain, an Arbitrum Orbit L2. The Veilify chain ID must be distinct from the settlement chain ID. Adding Robinhood’s public RPC to a wallet connects directly to Robinhood Chain; it does not provide Veilify’s veiled balances, proof generation or round scheduling. See Virtual Network for the wallet flow, RPC API for the proposed interface, and Deployment Addresses for the deployed contracts.

​
Robinhood Chain: settlement targets

These are the underlying blockchain networks targeted by the Veilify deployment. Their existing public RPCs are settlement endpoints, separate from the planned Veilify RPC.

Robinhood Chain Mainnet

Chain ID 4663 (0x1237). Gas token ETH. Parent chain: Ethereum.

Robinhood Chain Testnet

Chain ID 46630 (0xb626). Gas token test ETH. Parent chain: Sepolia.

​
Settlement configuration

Public RPCs are rate-limited. Use a provider endpoint for indexing and production. Source: Robinhood Chain: Connecting.

​
Compatibility

The pool needs Cancun opcodes, EIP-1153 transient storage (ReentrancyGuardTransient and escrow settlement) and the BN254 precompiles. Both networks were probed with read-only eth_call on 5 October 2026: Robinhood Chain runs ArbOS 61. Contract size limits are 96 KB runtime and 192 KB init code, well above Ethereum’s.
The probes show the features exist. They do not measure the gas cost of a full UltraHonk verification on Robinhood Chain. That is calibrated during the testnet phase.

​
Differences from Ethereum that matter

  • Two-leg fees: L2 execution plus L1 data cost. Gatekeeper reimbursement uses a configurable settleGasOverhead that includes the L1 data fee.
  • Soft confirmation, then finality: the sequencer confirms first; Ethereum finality follows. Indexers track both and handle transactions that are never included.
  • block.number returns an L1-style value. Indexers use the RPC’s L2 block numbers.
  • Sequencer-level screening happens at the chain level, separately from the Veilify gatekeeper.