OWP
Chain Key · Cross-Chain RIBBIT

Chain Key & Cross-Chain RIBBIT

The Other World arcade runs on the Internet Computer, but RIBBIT value lives on Solana. A 1:1 mirrored balance — kept in sync via HTTP outcall — lets the arcade read your holdings without ever moving the underlying token.

Open the Mirror Dashboard

01 · Wallet Sync & Mirrored RIBBIT

Solana is the source of truth. ICP is the accounting layer.

The Other World arcade runs on the Internet Computer — a chain built for fast, cheap, replicated computation. RIBBIT, the bounty token, lives on Solana — a chain built for high-throughput value transfer. The two chains do not share a native bridge, and the arcade does not custody your tokens.

Instead, the canister maintains a 1:1 mirrored balance on ICP. When you sync, the canister issues an HTTP outcall to a Solana RPC endpoint, reads the live RIBBIT balance of your linked wallet, and credits (or debits) the mirrored copy on your ICP identity to match. The arcade reads the mirror; Solana holds the value.

The mirror exists because the arcade needs a fast, on-chain ledger it can read on every cabinet load — without paying a Solana RPC fee per game frame. The mirror is the accounting layer that makes the arcade playable; Solana remains the custody layer that makes the value real.

1:1Mirror ratio
HTTPSync transport
0Tokens moved

02 · Before / After Sync

One sync. Two ledgers. Same balance.

Before and after wallet syncA Solana wallet on the left holding 5,006 RIBBIT, a sync arrow in the middle, and an ICP mirror on the right credited with the same 5,006 mirrored RIBBIT.SOLANA · ON-CHAIN5,006 RIBBITsource of truthSYNCHTTP outcall · 1:1ICP · MIRRORED5,006 RIBBITarcade accounting layer
Before sync

Solana wallet holds the real RIBBIT. The ICP mirror is empty or stale until you trigger a sync.

After sync

The canister has read your on-chain balance via HTTP outcall and credited the mirrored copy on ICP. The arcade can now read it.

03 · Cross-Chain Journey

From Solana wallet to arcade cabinet.

Cross-chain RIBBIT journeyA four-step flow: Solana wallet, HTTP outcall, ICP mirrored balance, and the arcade. The Chain Key Token path is annotated as the conceptual layer the HTTP outcall rides on.SOLANAwallet · RIBBITvalue secured hereHTTP OUTCALLread balanceChain Key pathICP MIRRORcanister ledger1:1 accountingARCADEbounty cabinetsreads the mirrorCHAIN KEY TOKEN PATH · CONTEXT ONLYa true ckRIBBIT is not feasible today — mirroring via HTTP outcall is the supported path
01

Solana custody

Your RIBBIT stays in your Solana wallet. The arcade never takes custody.

02

HTTP outcall

The canister reads your on-chain balance via a replicated HTTPS outcall to Solana RPC.

03

ICP mirror

The canister credits a 1:1 mirrored balance on your ICP identity — an off-chain ledger.

04

Arcade reads

Bounty cabinets read the mirrored balance to gate claims and weight payouts.

04 · Disclaimer

The mirror is not the token.

Mirrored RIBBIT on ICP has no standalone value — it reflects your Solana holdings. The mirror is an off-chain accounting ledger maintained by the canister; it is not a wrapped token, not a Chain Key Token, and not transferable. If you move your RIBBIT on Solana, the mirror becomes stale until you sync again.

A true ckRIBBIT Chain Key Token — where the Internet Computer itself holds and signs for Solana-side assets via threshold ECDSA — is not feasible on this platform today. The HTTP outcall mirroring path is the supported, audited mechanism.

Ready to sync your wallet?

Link your Solana wallet, trigger a sync, and watch the arcade read your mirrored RIBBIT balance in real time.

Open the Mirror Dashboard