Cave Collection Z

Sale termsCollection Z

The terms Collection Z, Cave's first batch, is sold under. Every number below is inside the terms digest, and you can recompute it from the bytes on this page.

cave-sale-terms/v5 4,444 · committed
Collection024277b607ce4edbf78fe2855aba562096d00264729168bd0ddea71bdf5b5f1e
Supply4,444
Manifest root0c56593e1b16bd513a4c88baf31d42602acd89db85aef2b0dcbc4e4bce108426
SaleOpen mint only: no tickets and no draw
Price5,000,000 zatoshi (0.05 ZEC) per item
Whitelist price1,000,000 zatoshi (0.01 ZEC) per item, for every whitelist applicant who links a Zyn account
Per account20 items at most, listed or not
OrderFixed once: the policy's concealed shuffle over no tickets, under the announced close's reveal
CloseAnnounced, with at least 1,152 blocks' notice
RevealClose + 100 blocks; announced drand round + 2,400
Confirmations6, for ZEC brought into Nap
SplitOf every payment, 90% to the collection's pool, 10% to the ZCaveDAO treasury
TreasuryZCaveDAO's: no key can spend it; it pays only on a passed proposal
DAO rules10 items back a proposal · votes run 8,064 Zcash blocks (7 days) · passes with more yes than no and at least 10% of items voting · fixed at the first proposal
Sale creditBurning ZCAVE (Solana, GQep…pump) or REGI (Arc, 0x93D5…60ae) gives credit worth what was burned at its USD price, at the lower median of the last hour (at least 10 readings) · credit pays for mints before ZEC.zy · nothing is behind it: the team funds none, and a mint it pays adds no ZEC to the floor
Policy digesta572a74778052829a768adb56f84404353ee5ad188b274b36b5fa58c68500b13
Terms digest25163fef565e4c47cce207bd3b8b0e854acb4df24dab07caa0c142aa38d0dd27
Replacesec3b0c2ffc7ae98423479d71d788ed47f975549e66626dc6f9df1b221d5004e8

Re-issued 13 Oct 2026, again before anything was sold. The fourth terms (ec3b0c2f…04e8, bytes) had the team pay ZEC into the sale behind burn credit. These do not: a burn of ZCAVE or REGI is credited what it was worth, with nothing behind it, so a mint it pays adds no ZEC to the floor. The floor is what is paid in ZEC.zy. Everything else is the fourth terms', and they are inside these bytes, whole.

Re-issued 13 Oct 2026, before anything was sold. The third terms (cd4cdc6a…e315, bytes) sold tickets in a draw, then claims, then an open mint. An item is now the entry to ZCaveDAO, so these go straight to the open mint: 0.05 ZEC each, 0.01 for whitelist applicants, at most 20 per account, in an order fixed once by the same kind of reveal. The policy, and so its digest, is unchanged.

Re-issued 10 Oct 2026, before any ticket was sold. The second terms (9267d58e…3d3c, bytes) gave up to 20 free tickets for burning the Solana token. The third gave credit for burning ZCAVE or REGI instead, paid for by the team so the floor is unchanged. Everything else, and the draw, is as before.

Re-issued 8 Oct 2026, before any ticket was sold. The first terms (f2c32420…a59e, bytes) sent the 10% to a team account and did not state the whitelist, the rising price, the DAO or the burn rule. The draw is unchanged — odds, shuffle, manifest, close and reveal — so the policy digest is the same.

Revised 23 Sep 2026. Every item gained Rarity and Rarity Rank, 3,555 Mole and Owl images were re-cut square, 12 Moth edges repaired and fourteen near-duplicate Moles replaced, which changed the manifest root. The version published on 19 Sep named root 02b01b16…8f19 and terms digest 159b454e…6267; nothing was sold under it.

  • 01The pool is what a redeemed item is paid out of. 90% of every mint payment funds it.
  • 02A change to these terms is a new digest, published here beside the one it replaces.
  • 03The opening is announced, not fixed here. The order the items come in is derived from it by rules already in these terms.
  • 04The reveal beats the operator: it lands on a drand round and a Zcash block that do not exist when the close is named.

How the sale runs

What the operator decides. Zyn cannot read Solana or Arc, so the operator's burn watchers decide which burns count and at what price; every burn is on its own chain and every credit on Zyn, so both are checkable. The operator orders transactions, so it can delay or refuse a mint, a burn's credit or a vote. The credit budget is on the ledger, where anyone can read it. It cannot change a price, the cap or the split once the mint starts, pick which item comes next, change a proposal's rules, or give itself items. The operator and replicas see which item voted.

Check it yourself

These are the canonical bytes — 382 of them, the exact input the digest is taken over (also at /cave-sale-terms-v5.hex).

00000012636176652d73616c652d7465726d732f7635ec3b0c2ffc7ae9842347 9d71d788ed47f975549e66626dc6f9df1b221d5004e800000143000000126361 76652d73616c652d7465726d732f7634cd4cdc6ab086ed51aa318093d34972f9 567bcd8d3b855d19bfdbfc857b44e315a572a74778052829a768adb56f844043 53ee5ad188b274b36b5fa58c68500b13024277b607ce4edbf78fe2855aba5620 96d00264729168bd0ddea71bdf5b5f1e0c56593e1b16bd513a4c88baf31d4260 2acd89db85aef2b0dcbc4e4bce108426010000000000004c4b4000000000000f 4240000000140101000003e80000000a00001f80000003e8040100000e100000 000a0000000200000006736f6c616e610000002c47516570654b474e704e6174 44524d506976465956734a6d665755734a68747a466842746843744c70756d70 0000000b6569703135353a353034320000002a30783933643562386335336565 373633633263343532326266306439353863653531616634333630616500

Standard-library Python. The domain and the payload are each length-prefixed before hashing.

from hashlib import sha256

payload = bytes.fromhex(open("terms.hex").read().strip())
domain  = b"cave.sale.terms.v5"
h = sha256()
h.update(len(domain).to_bytes(4, "big"));  h.update(domain)
h.update(len(payload).to_bytes(4, "big")); h.update(payload)
print(h.hexdigest())
# 25163fef565e4c47cce207bd3b8b0e854acb4df24dab07caa0c142aa38d0dd27

What this page does not yet prove

It proves what the terms are and that this digest is taken over exactly these bytes. It does not prove when they were written — nothing inside a document can establish its own age, and this is our own web server.

That takes a stamp on Zcash: the terms digest written into a transaction memo, so the chain dates it rather than us. That has not happened yet, and until it does, treat this page as a publication with our word on the timing.

← back to the cave