Oracle

Cross-chain

Move without moving the vault.

Track LayerZero delivery and mirrored NAV state. Sending remains unavailable until every route passes the production activation gate.

Route status

Robinhood Chain / Zero

Activation pending
Network IDs
Awaiting verified Zero coordinates
Assets
fIPO and FLOATS pending
Custody
Canonical assets remain backed on Robinhood Chain

Sending is intentionally disabled. Floats will not fall back to an unverified bridge or placeholder contract.

Mint fIPO on Robinhood Chain

Mirrored state

Latest NAV

Unavailable

Loading mirrored state…

fIPO on Zero is an OFT representation of canonical fIPO locked by the adapter on Robinhood Chain.

Trust and limitations

What the route depends on

Public disclosure
Canonical custody
Canonical fIPO and FLOATS remain locked in adapters on Robinhood Chain while OFT representations circulate on Zero.
Message security
Delivery depends on the configured LayerZero Endpoint, executor, required DVNs, peer contracts, and finality settings on both networks.
Operating controls
Governance can change bounded route configuration. A guardian can pause new outbound transfers, while only governance can unpause them.
Rate limits
Each token and direction has an independent onchain capacity. A transfer can be unavailable even when both networks are operating.
Mirrored NAV
Zero NAV is informational, can become stale, and never authorizes minting, redemption, options settlement, or vault accounting.
Activation policy
No route is enabled until peers, libraries, DVNs, executor, confirmations, roles, rate limits, and supply reconciliation pass verification.

Public activity

Bridge messages

0 records

Connect wallet