BRC-20 · Bitcoin silent payments

$shhhhh.

The first BRC-20 deployed with Bitcoin silent payments (BIP352). The deployer is a silent payment wallet, and every mint goes to one-time addresses nobody can link together.

Request an airdrop Trade on UniSat Verify the proof Deploy inscription

Token

Tickershhhhh

Max supply21,000,000

Decimals8

MintSelf-mint

Secondary market: $shhhhh on UniSat Marketplace ↗

Deploy

Inscription

a4e2f2b6…4fadci0

Transaction

a4e2f2b6b45b853b89e632e4b1bb02a43335f048cd951cbab978b43f73e4fadc

Block

968,871

Deployer (sp1)

sp1qq2p366tdq6n8y30s6n3xz0qspa86n9am65zgcgq0nn2pu3je0szrxqm328h0fec8ljkd2tdmdskqv6gmpy8mfml2gj6xs58jpeunfy8mfycfkve3

On chain it shows as

bc1pn2px8ggfznjdk07ughw88m3nj6glh4ngjwz5jpmeyqknjqcr7utselnkkd (one-time address)

{"p":"brc-20","op":"deploy","tick":"shhhhh","max":"21000000","lim":"21000000","dec":"8","self_mint":"true",...}

How it stays silent

A silent payment address never touches the chain. Coins sent to an sp1 address land on a brand-new one-time address that only the receiver's wallet can recognize.

So explorers show a normal bc1p address as the owner. Everyone can see it exists; nobody can tell which wallet it belongs to, or link it to any other payment.

That also makes it impossible to prove, unless you publish a proof. A BIP374 DLEQ proof shows the deploy output was derived from our sp1 address, without revealing any private key. Check it below.

Verify the proof

Runs entirely in your browser. It reads the deploy transaction from the Bitcoin blockchain (via mempool.space), recomputes the silent payment output from the sp1 address, and checks the DLEQ proof.

Prefer the command line? Proof + Python verifier · proof.json

Airdrop

$shhhhh is only minted to silent payment addresses. Have an sp1 address? Request an airdrop.

… / 20,000 wallets

Only the first 20,000 silent payment wallets can join the airdrop.

Request an airdrop