01
Encryption is not anonymity
Who talks to whom, when, and how often is visible to the relay. So are Null IDs, handles, public keys, and controlling addresses.
Protocol
Null / EVM
Your wallet has an inbox.
A wallet-native private communication network — encrypted messages, permissioned contact, and settlement inside the same conversation. This page is the whole position: how it works, what runs today, and what the token is for.
- Network
- Robinhood · 4663
- Code
- Relay + client
- Token
- NULL · ERC-20
- Encryption
- nacl.box
Nothing on this page is an offer to sell or a solicitation to buy any asset. Verify every address and every link against the project's own channels before you transact.
01At a glance
Encryption
nacl.box
x25519 · xsalsa20
Network
Robinhood Chain
The launch network
Chain ID
4663
0x1237
Block time
~100 ms
Sub-second finality
Gas token
ETH
18 decimals
Settlement
USDG
Unconfirmed
The chain figures above are read from the client's own configuration rather than retyped into the page — change one in lib/chain.ts and every surface follows it.
02The position
Value found its rails.
Everything around it did not.
- 01
A wallet can send value and nothing else
Every negotiation around an on-chain transfer happens somewhere else — a group chat, a DM, an email thread — where the counterparty is a screen name, the agreement is a screenshot, and the platform holding all of it is not the one holding the money.
- 02
The address is already the account
It is verified, portable, and carries a keypair. Messaging keyed to it needs no phone number, no email, and no signup: prove the address, derive a messaging key, publish the public half. Two signatures, and the inbox exists.
- 03
Attention is the thing worth pricing
A stranger cannot message you; they can knock, and a knock can carry a refundable bond. Accepted conversations carry payment requests that settle on-chain. That is the revenue surface — pricing access, not reading messages.
03How it works
Four steps from an address to a paid conversation
Every step below is running code in this repository. Nothing in this sequence is a mock-up, and nothing in it touches a smart contract.
- 01
Connect
Connect an EVM wallet and sign in. Two signatures: the first proves you control the address, the second derives the messaging keypair.
No password, no email, no phone number
- 02
Claim an ID
Publish a handle and a public key against your address. Anyone can resolve the handle to the key; nobody can read a message without it.
Relay record — no gas, no transaction
- 03
Knock
You cannot be messaged without permission. A stranger sends a knock; you accept, reject, or block it. Nothing reaches the inbox before you decide.
Blocking is silent — a blocked knock goes nowhere
- 04
Talk, then settle
Messages are sealed to your published key with a fresh ephemeral keypair. A payment request lives in the thread and settles on-chain in USDG.
Amounts carried as integer minor units, 6dp
Before you start
- Wallet
- Any EVM browser wallet
- Network
- Robinhood Chain · 4663
- Gas
- ETH — the chain's native token
- Settlement
- USDG · address unconfirmed
04Token & supply
A distribution on the table, not a cap table
Verify
Check every contract address and every link against the project's own channels before you transact. Null will never message you first, and will never ask for a seed phrase or a private key.
The instrument
- Symbol
- NULL
- Total supply
- 1,000,000,000
- Standard
- ERC-20
- Network
- Robinhood Chain · 4663
- Contract
- To be announced
Distribution — 100% of supplyFloat at listing 6.0%
| Allocation | Share | NULL | Unlock |
|---|---|---|---|
| Relay incentives | 32% | 320,000,000 | 48-month linear emission |
| Ecosystem & grants | 18% | 180,000,000 | 6-month cliff, 36-month linear |
| Core contributors | 17% | 170,000,000 | 12-month cliff, 36-month linear |
| Early backers | 15% | 150,000,000 | 12-month cliff, 24-month linear |
| Treasury | 12% | 120,000,000 | Released by governance vote |
| Public distribution | 6% | 60,000,000 | Unlocked at listing |
05Connect
Point a wallet at the network
Robinhood Chain runs ETH gas and roughly 100 ms blocks. These are the parameters the client itself uses.
Network nameRobinhood Chain
Chain ID46630x1237
RPC endpointhttps://rpc.mainnet.chain.robinhood.com
Explorerhttps://robinhoodchain.blockscout.com
Gas tokenETH18 decimals
USDG addressUnconfirmedLeft unset until the canonical deployment is published — a placeholder here is an address someone could send funds to.
Where to look next
06What's built
8 capabilities. 3 of them finished.
The relay, the encryption, and the permission layer run today. Settlement, bonds, groups, and everything that would make this a network do not.
3Working2Partial3Not built
Wallet sign-in
Nonce, signature, session token. Two signatures — one proves the address, one derives the messaging key.
WorkingEncrypted messaging
nacl.box sealed against the recipient's published key, a fresh ephemeral keypair per message. A test asserts the relay never holds plaintext.
WorkingKnock permission layer
Accept, reject, block. A blocked sender's knock returns 201 and goes nowhere — telling them otherwise invites a fresh identity.
WorkingPayment requests
Requests, receipts, and integer minor units end to end. Settlement records the hash the client supplies; nothing reads the chain to verify it.
PartialAnti-spam bonds
The bond amount travels with the knock. No contract locks it and no contract returns it.
PartialGroups and file sharing
Conversations are one-to-one. Group keying and file transport are Phase 2 work.
Not builtMulti-device history
Keys re-derive from a signature; history does not transfer. Your sent copy lives in localStorage by design.
Not builtRelay decentralisation
State is a single JSON file today. Fine for an MVP, not for a network, and not rate-limited.
Not built
server/test/flow.test.ts asserts the relay never holds readable message content. That test is the guard on the property — if the relay is ever made to handle plaintext, it fails.
07Order of work
No dates, because there are none to give
Each phase is ordered against the one before it. Nothing here carries a delivery commitment, and Phase 01 exists because nothing in Phase 00 has been reviewed by anyone outside the project.
Four passes over
the same network,
one of them lit
- Phase 00Running
The protocol, in working code
- Relay, encryption, and the knock layer running end to end
- The archive published as 31 records
- Robinhood Chain wired in as the launch network
- Phase 01Next
Make it safe to look at
- Independent cryptographic review and application-security testing
- Rate limiting, abuse handling, and key rotation
- A confirmations worker that verifies settlement against the chain
- Phase 02Later
Make it a network
- Multiple relays, with delivery that survives any one of them
- Groups, file transport, and multi-device history
- Bonds settled by contract rather than recorded by the relay
- Phase 03Later
Hand it over
- Governance over treasury and emission
- Smart-contract audits published in full
- Legal and securities review before any distribution
08Risk & disclosure
Read this part twice
Encryption is a property of the message, not of the person sending it. Everything below is a limitation the project already knows about and has written down.
02
Payment metadata is in the clear
Amount, purpose, and participants are stored unencrypted so receipts can be rendered, and settlement happens on a public chain.
03
Nothing here has been audited
No security review, no cryptographic review, no contract audit, no threat model. This should not be deployed, and money should not be committed to it, until all four exist.
04
Null will never message you first
Null will never ask for a seed phrase or a private key, and will never open a conversation with you. Verify every address and every link against the project's own channels; an unsolicited offer is a fraud.
Nothing on this page is an offer to sell or a solicitation to buy any asset, nor is it investment, legal, or tax advice. Independent legal review, cryptographic review, application-security testing, smart-contract audits, and privacy threat modelling are all required before any production deployment, and none of them has been done. Null will never request a seed phrase or a private key.
The application is live and needs no permission from us
Open the
inbox
An EVM wallet in the browser is all the app needs. It talks to a relay you can run yourself, and it will tell you plainly when that relay is not there.