5 rails in · 1 envelope out · MIT-licensed
Hive Rosetta

Translate any rail receipt into hive-vcr-1.

Paste a Stripe webhook, a Base tx hash, a Solana signature, an x402 proof, or raw payment JSON. Get back a signed hive-vcr-1 envelope that closes against any rail. Adopt once. Settle everywhere. Survive every rail migration.

Translate a receipt
The translator

Paste in. Signed envelope out.

Base tx
x402 proof
Stripe webhook
Solana sig
Raw JSON
Load example for selected rail
Source Rail
Token ID
Profile
nano
Signature Status
signed

Translated hive-vcr-1 envelope

View public receipt Verify envelope
5 rails · 1 envelope

The substrate that survives rail migration.

Base
Settlement tx hash → hive-vcr-1 with base_tx_hash and USDC amount
x402
x402 proof payload → hive-vcr-1 with full settlement reference and validator DIDs
Stripe
Webhook event JSON → hive-vcr-1 with stripe_event_id and idempotency key
Solana
Transaction signature → hive-vcr-1 with solana_sig and slot
Ethereum
Mainnet tx → hive-vcr-1 with eth_tx_hash and block height
Raw JSON
Any rail-shaped payload — Hive normalizes the fields it can identify and signs the envelope
Why this matters

Rails are plural and forever.

Base settles on Base. Stripe settles on Stripe. Solana settles on Solana. A merchant who picks one is hostage to it.

Hive Rosetta makes the rail invisible. A merchant adopting hive-vcr-1 for one rail gets every other rail for free — current and future. The envelope is the contract; the rail is an implementation detail.

When a new rail emerges (and it will), we add it in one commit. Your merchant code does not change. Your audit history carries forward.