privacy-first launchpad · meteora dbc · tor
No account. No wallet extension. A burner wallet is generated in your browser tab, every transaction is decoded before you sign it, and the whole site also runs as an onion service. Every fee fills one public vault that pays $ZEROID holders.
$ tail -f trades.log live
connecting…
coins launched
—
fees → vault
—
vault balance
—
paid to holders
—
why zeroid
leave less behind
git diff pumpfun..zeroidwhat you leave behind
--- a/pumpfun +++ b/zeroid @@ what you need @@ - an account- a wallet extension- your IP in someone's logs- blind-signing whatever the site sends+ a burner in your tab+ an onion address+ a transaction inspector+ every fee in one public vault
./session how a visit worksdocs →
+--------------------+ | 1. generate | +--------------------+
a fresh key is born in this tab
+--------------------+ | 2. fund | +--------------------+
send SOL from anywhere
+--------------------+ | 3. launch / trade | +--------------------+
on the Meteora curve
+--------------------+ | 4. nuke | +--------------------+
withdraw, wipe, close the tab
The key never leaves the tab: no cookies, no local storage, no service worker. Your phrase, IP and access logs are never stored on our side. Nuke sends what is left to any address you choose, then zeroes the key in memory.
trenches
latest coins
| coin | mcap | curve | fees → vault | age |
|---|---|---|---|---|
| loading… | ||||
vault
every fee ends up in one place
fees → vault → holdersopen the vault →
every trade on every coin | trading fee (partner + creator share) v +----------------------+ | ZEROID VAULT | public address, on-chain +----------------------+ | snapshot of $ZEROID holders, sent manually v holders above the minimum, pro-rata in SOL
Payouts are sent manually by the ZEROID team. Every payout is on the public ledger with its snapshot and transactions. No schedule is promised.