IVlWVlWI

How to buy a stamp

Send shielded ZEC with a one-line memo. A few minutes later a dust payment lands at your reply address, and its memo holds the key.

There is no account, no email and no card. There is also no refund path and no support channel that can identify you. Read the pre-flight list before you send anything.

WHAT YOU ARE BUYING

One Venice API key, minted from the treasury account, carrying three properties.

  • Private models only. The key is minted with modelPrivacy: PRIVATE_ONLY. It can call models Venice marks private, including the TEE and end-to-end encrypted ones. It cannot call anonymized models.
  • A DIEM cap per UTC day. One DIEM is about one dollar of Venice inference. The cap resets daily and is not a total. A tier M stamp is one DIEM every day for seven days, not seven DIEM to spend at once. Unused allowance does not roll over.
  • An expiry. Set at mint time to the tier's length and printed in your memo. After that instant the key returns 401 and nothing renews it.
TIERDIEM/DAYDAYSPRICEZEC NOW
S0.53··
M17··
L330··

loading the live quote from the clerk…

You do not choose a tier you did not pay for. The clerk grants the highest tier your payment covers, whatever the memo asked for. The tier letter only shapes the message you get back if you fall short.

PRE-FLIGHT

Every one of these corresponds to a way people have lost money.

  1. Check the clerk is live, not a testFetch /status.json. network must read mainnet and dryRun must read false. A dry-run clerk mints fake keys prefixed DRYRUN- and your payment buys nothing.
  2. Take the address from this origin, then verify it elsewhereCheck it against the X account before sending. A privacy-branded checkout page is an obvious target for an address swap.
  3. Check free capacity/status.json carries available DIEM per day. If it is below the tier you want, wait. A payment arriving with no capacity is consumed and answered with a sold-out memo.
  4. Use a wallet you control that can write a memoNot an exchange. The rule is not "shielded", it is "shielded and you can type a memo".
  5. Copy your reply address from your wallet's receive screenNever type it. It starts with u1 or zs1.
  6. Check the last six characters against your walletThe clerk verifies the address checksum, so most typos are refused before a key is minted. A checksum is not proof of ownership: a typo that still produces a valid address delivers your stamp to a stranger, and nothing can detect that.
  7. Read the live ZEC price, then add five to ten percentThe price applied is the one in force when the clerk processes your note, not when you read the page. Tolerance for underpayment is three percent.
  8. Send one payment per stamp, in its own transactionDo not batch two purchases into one transaction. The wallet backend reports one note per transaction, so a second memo-bearing output is invisible and its money is kept.
  9. Check your funds are spendableZEC that has sat in the Orchard pool since before July 2026 is behind the Ironwood turnstile and must be migrated first. An Ironwood-ready wallet does this for you.
  10. Decide your network posture before you payA lightwallet client tells its server your IP however good the on-chain privacy is. If that matters, configure Tor in the wallet first.

THE MEMO

This is the whole interface. One line, inside the shielded payment, encrypted.

stamp M reply:u1yourfulladdresshere

Always write reply: in front of the address. The parser looks for a bare address first and falls back to whatever follows reply:. If your wallet hands you an address shape the parser does not recognise, the reply: form is the only thing that survives.

BUILD IT


      
      

This runs in your browser. The address is not sent anywhere.

FORMS THE PARSER ACCEPTS

MEMORESULT
stamp M reply:u1…Tier M, address read. The form to use.
stamp M u1…Same. A bare address anywhere is found.
STAMP:M reply:u1…Same.
tier=M reply:u1…Same.
M reply:u1…Same.
u1… with no tierAddress read, tier unknown. Best tier your payment covers.
Unparseable, but with an addressHanded to a Claude clerk, address replaced by a placeholder.
Anything with no recognisable addressPayment consumed. Nothing sent. Nothing recoverable.
PREFIXES

Recognised as a bare address: u1 and zs1, plus utest1 and ztestsapling1 on testnet. The draft zu1 and tu1 forms are not matched in bare form; put them after reply: and understand that delivery to those prefixes is untested. A transparent address is never accepted, because a transparent output has no memo field to deliver into.

SIZE

A Zcash memo is exactly 512 bytes. Overflow is a hard error at the wallet, not a truncation, so an oversized memo is refused rather than half-delivered. The line above runs to roughly 230 bytes with a three-receiver unified address. Do not add greetings or order numbers. Count bytes, not characters: non-ASCII costs two to four bytes each.

WALLETS THAT WORK

Last verified 21 September 2026. This table dates faster than anything else here. In the nine months before that date the ecosystem lost zcashd, lost Nighthawk's send capability, lost Ywallet, renamed its flagship wallet and changed shielded pools. Re-check before you rely on a row.

WALLETSHIELDED SENDMEMOVERDICT
Zodl (mobile)yesyesUse this one.
Zingo (mobile)yesyesGood second choice.
zingo-cli, Zingo PCyesyesWorks. Current desktop builds carry an experimental tag.
ZkoolyesassumedViable. Its pool migration is private, which is an advantage.
Cake WalletyesassumedViable. Memo field not verified by us.
VizoryesassumedViable. Memo field not verified by us.
Zallet (RPC)yesyesBeta. Many old RPCs are not ported.
EdgeyesunverifiedDo not use until someone confirms a memo field.
YwalletnonoBroken and unmaintained.
NighthawknonoSending was removed. Export your seed elsewhere.
Exodus, Trust, Coinbase Wallettransparent onlynoCannot be used.
Ledger LivenonoCannot be used today.
zcashd, zcash-cligonegoneThe software halted itself in July 2026.

Zodl used to be called Zashi. The team left Electric Coin Co in January 2026 and renamed the app in February. Same seed, same balances, no migration. The old package identifiers are expected, not a spoof.

The rule underneath the table: a memo only exists on a shielded output. Transparent-only wallets are disqualified by construction, not by policy.

SENDING, IN ZODL OR ZINGO

  1. Tap Send and paste the clerk addressThe wallet marks a transparent destination as not private. The clerk address is shielded, so you should not see that warning.
  2. Enter the amount from the live table, plus five to ten percent
  3. Open the memo fieldIt only appears when the destination is shielded. If you cannot find it, the destination is not shielded and you should stop.
  4. Paste the memo line and check it on screenOne line, the whole address visible, no line break inside it. Compare the last six characters against your own receive screen.
  5. Send, then waitThree confirmations, a few minutes. The clerk polls every thirty seconds.

SEND HERE

CLERK ADDRESS ·

loading from the clerk…

AFTER YOU SEND

A dust payment of 0.0001 ZEC arrives at your reply address. Its memo is the stamp. Some wallets hide amounts that small or file memo-only transactions separately, so find out where your wallet shows memos before you start waiting.

Nothing back after an hour? Read troubleshooting before sending again.

BURN LANE

After the IVLW launch on Elysium, the Hyperliquid L2, you can also burn IVLW there and claim a stamp with the transaction hash. Gas is paid in HYPE. A burn counts once it is final on HyperEVM, about fifteen minutes after you send it. The burn is public and linked to your wallet. Only the delivery is shielded. If unlinkability is why you are here, pay with shielded ZEC instead.