Disposable identity protocol · concept

NULLID

An identity with no identity.

ConnectExecuteDisappear
Run the simulationHow it works
The problem

Every dApp you connect to sees everything.

A normal connection hands an application your main address: its balance, its history and standing permissions that outlive the visit. NULLID puts a temporary wallet in between, funded for one job and gone after it.

Direct connection

Main wallet → dApp

Balance in reach$50,000
Address revealedMain
PermissionsUntil revoked by hand
Through NULLID

Main wallet → disposable → dApp

Balance in reach$200
Address revealedTemporary
PermissionsExpire on their own
Simulation · runs in your browser, touches no wallet

Open a session. Watch it disappear.

Addresses here are random strings and time runs fast. Nothing is sent anywhere.

01 Connect
02 Execute
03 Disappear
No active session
—
Limit—
dApp can see—
Expires in—

idle. main wallet is not connected to anything.

Core functions

Five limits between you and a bad contract.

01Disposable Wallets

A fresh address for every connection. Used once, then abandoned.

02Hidden Identity

The dApp connects to the temporary address. Your main one is never the party it talks to.

03Spending Limits

The session holds only what the operation needs. A drained session costs the limit, not the wallet.

04Expiring Permissions

Approvals carry a deadline and end without you remembering to revoke them.

05Session Isolation

Each session is separate. What happens in one does not reach the others.

Step 1Connect.

NULLID creates a temporary address and gives it the funds and permissions for this one task.

Step 2Execute.

The application deals with the temporary wallet only. $200 for a $200 operation.

Step 3Disappear.

Permissions run out, what is left returns, the address is never used again.

Token

$NULLID

The token of the NULLID concept. Check the contract address against our X account before you interact with it. Ideally from a wallet you can afford to lose.