01 / THE THESIS

Privacy should be owned, not implied.

Today privacy is a promise someone else makes about data you cannot reach. A policy. A provider. A jurisdiction. Every one of them survives being wrong.

Owned privacy is a key you hold. Without it the data does not open — not for the platform, not for an interceptor, not for us.

REACTIVE ANONYMITY

Data is sealed by two keys and opens only for the pair it was meant for. The publishable half is re-derived on every request, so an intercepted key is already dead.

02 / THE MECHANISM

Two keys. Re-derived every request.

Both parties contribute to the key that seals a transaction. Neither half opens it alone, and the publishable half never repeats.

01 PAIR

Both sides contribute key material. Neither holds a value that opens the exchange alone.

02 DERIVE

A key is derived for this transaction only.

03 SEAL

The payload is sealed to the recipient. In transit it is opaque to everyone else, operator included.

04 ADVANCE

The key just used is retired. It cannot reconstruct the next one or the last one.

STATED PRECISELY

An authenticated key exchange with a per-message ratchet — not a rotating code from a fixed seed. A rotating code collapses when its seed leaks; a ratchet does not expose the messages before or after a compromised key. Construction specified in RAN-01.

03 / FIRST APPLICATION

Anonymous governance.

Token votes are public. Holders self-censor, and a large position that reveals intent early has published a trade.

A sealed ballot opens only into the tally. Verifiable in full, attributable to no one — including by us.

04 / LIMITS

What we do not claim.

RAN proves facts about assets. RAN never moves assets.
Nothing is deployed

RAN is a specification. No verifier is live and no verification has been performed.

Sealing a payload does not hide the network path

Encryption conceals contents, not the fact that two addresses spoke. Protecting the IP layer needs relaying, and it is not built.

Anonymity is crowd size

A group of forty gives one-in-forty. No engineering changes that number, so the size is published in the interface.

05 / STATUS

Every claim, with its status.

RAT ERC-20 on Base, fixed supply 1,000,000,000VERIFIED
Contract 0x72D9…A9BdVERIFIED
RAN specificationSTATED
Two-key transactional sealingPROJECTED
Per-request key re-derivationPROJECTED
Anonymous governancePROJECTED
Network-address protectionPROJECTED — NOT SOLVED BY ENCRYPTION ALONE
Verification counterREMOVED — NO VERIFIER DEPLOYED
Migration 1:1 lockREMOVED — NO MIGRATION CONTRACT
Fund allocation targetsREMOVED FROM PUBLIC SURFACE
01 / POSTURE

No public raise. No allocation figures on a public page.

RAT is a deployed ERC-20 with a public market. This page is not an offer and does not solicit one. No treasury breakdown, allocation target, or use-of-proceeds figure is published here — those previously appeared on this site and have been withdrawn pending a securities posture review.

Materials of that kind are shared only in a gated data room, with qualified counterparties, after that review is complete.

02 / INQUIRY

Direct contact.

Design partners and contributors first. Capital conversations follow RAN-01 and a live testnet, in that order.