Yours to prove.
Null to everyone else.
Null Bond seals an asset claim into a bond: one hash on Robinhood Chain that only your receipt can open. Keep it, hand it over, and prove it to one person at a time.
Prove one thing.
Null the rest.
A connected wallet shows a site everything you have ever done. A receipt shows it one bond, and nothing next to it.
The site sees your history
- every balance you hold
- every transfer, in and out
- every counterparty you touched
- when you are active, and how much
- 0x7a3f…c91e · 0x19bd…44a0 · 0x…
The verifier sees one bond
- the asset sealed in that bond
- its 32-byte commitment
- the anchor transaction, if any
- one answer: true or false
- nothing else you own
Seal, keep, prove. All three run in your tab.
Seal
SHA-256 over the asset, a 16-byte salt and a 32-byte key. Anchor it and Robinhood Chain records 32 bytes, nothing more.
Keep
The receipt stays in your browser, with an encrypted backup you can export. Lose both and nobody can open the bond again.
Prove
Your counterparty pastes the receipt into Verify and gets one answer back: true or false.
Four moves. Each one leaves 32 bytes behind.
Seal a bond
Your browser hashes the asset with a fresh salt and a key used once. The hash names neither the asset nor its keys.
Receive a bond
Open a package with its passphrase and the bond is resealed under a new key generated in your browser.
Hand over a bond
Seal the receipt in an AES-GCM package behind a passphrase. The recipient reseals it under a fresh commitment. Your copy keeps verifying until you discard it.
Prove a bond
Send one receipt to one counterparty. Their browser recomputes the hash and learns that bond, and nothing else.
The token opens the gate.
The bond contract is designed to mint only to wallets that hold $NULL, and the fee hook to burn 80% of every fee it takes. Both contracts are on the roadmap: neither is deployed yet.
Sealing, hand-overs and verification are live in the console today. Anchors are plain Robinhood Chain transactions until the bond contract is deployed against $NULL.
How $NULL launches, and the risks: Terms and Conditions
Your vault never leaves the tab.
Receipts are stored in your browser. No account, no server, no tracking in the console.
- Every bond you seal or receive, with its status
- Encrypted backup file, locked with your passphrase
- Discard a receipt and that bond can no longer be proven
A wallet signs 32 bytes. That's all it touches.
Anchoring sends a zero-value transaction on Robinhood Chain that carries the commitment. Nothing else from your vault is ever sent.
- Any EVM wallet: MetaMask, Rabby, Coinbase Wallet
- Robinhood Chain is added to your wallet in one click
- Use a fresh wallet if you don't want the anchor tied to your main one
Settle with a bond.
Handing over is the payment. Seal the receipt into a package, send the passphrase through another channel, and the recipient reseals it under a key only they hold.
Show the proof.
Keep the portfolio.
One receipt, one counterparty, one bit. The rest stays null.
Ownership, nulled.
Seal an asset into a bond, hold it under a key that has touched nothing else, and prove it whenever someone asks, without handing over the rest of your portfolio.