Terms

House of Zaldwin sells 7,711 NFTs for ZEC on the Zcash blockchain. This page states what you get, what you do not, how the technical side works today, and how you can verify every claim yourself. Gold words show a plain explanation when you hover over or tap them.

Each NFT is one masked king: a 26 by 26 pixel image, its traits, a token number from 1 to 7,711, and a record of who owns it (NFT means exactly that: one number, one owner). Zcash has no NFT standard on mainnet yet, so today the ownership record is our ledger: a signed list that maps every token number to a shielded address. The ledger is published, and its SHA-256 hash is written into a Zcash transaction every day, so anyone can check that the ledger they see is the ledger that was hashed. When Zcash Shielded Assets activate on mainnet, each entry becomes a real on-chain asset in the owner's wallet (see below).

Before the mint, the SHA-256 of every image and one hash of the ordered list are written to Zcash as well. The images cannot be swapped afterwards without breaking those hashes.

The collection is inspired by Baldwin IV, King of Jerusalem from 1174 to 1185. He had leprosy from childhood and ruled with his face covered by a mask or veil, which is where the masked kings and the line "every face is public, every king is not" come from. The numbers in the collection are taken from his life:

• 7,711 NFTs: 1177 read backwards. On 25 November 1177 Baldwin beat Saladin's army at Montgisard with a few hundred knights.
• 16 Jerusalem NFTs, the sixteen highest-ranked: Baldwin was sixteen at Montgisard.
• 24 Montgisard NFTs, each with a trait no other NFT has: Baldwin died at twenty-four.
• 26 by 26 pixels: the 26,000 men Saladin is recorded to have brought to Montgisard.
• 13 hours of whitelist: Baldwin was crowned at thirteen.
• 0.01177 ZEC auction floor: 1177 again.

The 7,711 images were not drawn one by one, but every part of them was. Each trait (every mask, crown, robe, background and so on, 124 variants across 10 layers) is a hand-drawn pixel sprite. A small program, the engine, then combines those hand-drawn parts systematically: it picks one variant per layer, rejects duplicates, and composes the 26 by 26 image. No AI image generator was used at any point: every sprite is placed pixel by pixel in code and checked by eye, and the engine only combines them. It does this from a fixed seed. The engine (core.js) runs in your browser on this site, and the seed is printed in the provenance file. That means you do not have to trust us:

What we publish, and when. Three files, in three steps, each one hashed to the chain before it matters:

• Before the whitelist opens: provenance.json, the ordered list of 7,711 image hashes (SHA-256 of each 26 by 26 PNG), one hash of the whole list, and the founders' two token numbers. Not the images, not the traits: only the fingerprints. The SHA-256 of this file is written into a Zcash transaction as an OP_RETURN output, in the open, before the first payment.
• Reveal I, when the whitelist closes: the images and traits of every NFT minted in the whitelist. Each image hashes to the fingerprint already on chain.
• Reveal II, when the auction closes: all 7,711 images and traits, the engine (core.js) and the seed. From this point anyone can regenerate the whole collection and confirm it matches the fingerprints published before the whitelist. The seed is held back until then because it reveals everything.

How to check it yourself. You need a computer with Node.js, nothing else:

1. Download provenance.json, core.js and verify.js from this site (all three will be linked on the Ledger section when published).
2. Open a terminal in that folder and run node verify.js. The script regenerates the 7,711 images from the seed with core.js, hashes each one, and compares every hash with the list in provenance.json. It prints the SHA-256 of the file, the SHA-256 of the list, and any mismatch.
3. Take the printed file hash and look up the transaction we name on the site in any Zcash block explorer. The OP_RETURN output contains that hash, and the block height is older than the whitelist.
4. After the mint, the daily ledger works the same way: download ledger.json, hash it, find the hash in that day's transaction.

If any of these checks fails, the collection is not what we said it was, and you should say so loudly. That is the point of publishing them.

Ranks are computed from the list the same way, by anyone: the fewer NFTs share a trait, the more it weighs, and the sum of the weights orders the collection from 1 to 7,711. No committee, no hand-picked tiers.

The two founders keep one NFT each. Everything about them is written down before anyone pays: their token numbers are in the provenance file, so they cannot be swapped later for rarer ones; neither is in Jerusalem or Montgisard, and both carry ordinary rarity. When the whitelist opens, the founders pay the whitelist price for them from their own wallets, like everyone else, and publish the transactions. No other reserve, no treasury, no free NFTs.

Zcash Shielded Assets (ZSA) let assets other than ZEC live inside the Orchard shielded pool, with the same privacy that ZEC itself has: who holds what, and who sends what to whom, stays hidden. The technical basis:

• ZIP 224: the Orchard shielded protocol that ZSA builds on.
• ZIP 226: transfer and burn of shielded assets inside Orchard; each asset has its own identifier and its own notes in the pool.
• ZIP 227: issuance of shielded assets by an issuer key, with supply defined by the issuer; an asset issued with a supply of one is a non-fungible asset.

Status at the time of writing (September 2026): ZSA runs on the Zcash testnet and is planned for a coming Zcash network upgrade on mainnet. The activation height and date are decided by the Zcash protocol process (the Electric Coin Company, the Zcash Foundation and the community), not by us. We do not control that timeline and we do not promise a date.

What we commit to when ZSA activates on mainnet:

• We issue one shielded asset with a supply of one per NFT, 7,711 in total, from a published issuer key.
• Each ledger entry can be claimed once. The holder proves control of the shielded address written in the ledger (a signed message or a memo challenge from that address), and we send that NFT's asset to it. Claims are 1:1 and free apart from network fees.
• After the claim, the NFT is held in the owner's own wallet and can be sent or sold like any shielded asset. Our market moves on-chain with it and stops acting as escrow.

This is our intent and a commitment of effort, not a guarantee of a third-party protocol's timeline, of wallet support, or of the final form of the specification. If ZSA changes before activation, we follow the final specification and say so on this page.

Payments are Zcash transactions you make from your own wallet to our shielded address. No wallet is ever connected to this site. Whitelist payments that match a valid ticket mint an NFT. Auction bids are payments; when the auction closes, losing bids and any amount above the clearing price are refunded to the refund address in your memo. Payments with a missing or unreadable memo are held for manual review and refunded when the sender can be identified; if they cannot be, they cannot be refunded. Keep your memo exact.

Until ZSA activates, trades on our market are settled by us as escrow: the buyer's payment is received by us, the ledger is updated, and the seller is paid minus a 5% fee on the sale price. That is the whole fee; there is no separate marketplace commission. Confirmed trades cannot be reversed. Listing is free.

No token, no governance, no yield, no guaranteed floor. House of Zaldwin is not affiliated with the Electric Coin Company or the Zcash Foundation. Nothing here is investment, legal or tax advice. You are responsible for the laws that apply to you.

We never ask for seed phrases, spending keys or viewing keys. The only official places are zald.win, X @ZaldwinZEC, Discord discord.gg/zaldwin and Telegram t.me/ZaldwinZEC. Anyone else claiming to be us is not us. Mint addresses are announced on this site and on those channels only, never in a direct message.

Last updated: September 2026.