# Zecboat.com Wake-v1, custom Halo 2 circuit for note lineage **URL:** \ **Category:** Applications\ **Created:** [October 13, 2026, 10:39am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166 "2026-10-13T10:39:37Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![kworks](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@kworks](https://forum.zcashcommunity.com/u/kworks)\ **Post date:** [October 13, 2026, 10:39am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/1 "2026-10-13T10:39:37Z")
Github: [Zecboat: Wake v1, a custom Halo 2 circuit for note lineage · Issue #487 · ZcashCommunityGrants/zcashcommunitygrants · GitHub](https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/487) **Project Summary** Wake-v1 is a custom Halo 2 circuit for note lineage: it lets the user who receives a layer two zcash shielded asset check, from the chain, that the note in their hand descends from the issuer’s original note. It needs no trusted setup and no consensus change. The proofs travel inside the transfer itself, so no server stands between the sender and receiver. Wake-v1 ships in Zecboat 0.7.1-beta today; this grant takes it through an independent review to a wallet that can say “verified”. **Proposed Solution** Wake answers the receiver’s question with a zero-knowledge proof for each transfer, and reveals no key and no amount. In Orchard, every output note carries a value ρ. It equals the nullifier, the public mark a spent note leaves, of the note spent in the same action. For each hop, Wake proves that the previous holder knew a note whose commitment is in the note commitment tree at a stated anchor. It also proves that the nullifier derived from that note’s own keys equals the ρ of the next note. Chained back to the genesis outputs named in the issuer’s closed registry, the proofs show the note in hand descends from an original unit. The chain of proofs is the unit’s “lading”. It travels inside the transfer itself. The Knotline writes one knot per transfer: the newest proof, sealed to the receiver, in the memos of the same transaction. The transfer memo commits to the lading’s hash. A sealed file moved by hand is the only fallback. The receiver’s wallet reads the line back from the chain and verifies it. It checks that the anchors exist at the stated heights, that the nullifiers are on chain, and that the first note is a registered genesis output. It checks that the last ρ matches the note in hand, and that every proof verifies under a pinned key. The proofs are checked on the receiver’s machine. The chain’s answers come from their own node, or from their light server when they run none. Design choices a reviewer will care about: Wake-v1 is a Halo 2, so there is no trusted setup. It uses the same proof system and curves as Orchard. The circuit is derived by deletion: orchard’s Action circuit with 247 code lines removed, one constraint added and one made unconditional. There are two circuits (WAKE\_HOP, WAKE\_GENESIS) at K = 11, differing in that one constraint. The diff is in the repository. Every constraint has a failing test. Ten attacks are each caught by exactly one named constraint, shown by building the circuit with that constraint removed. The verifying keys are pinned. The wallet refuses proofs under any other key. The status is stated honestly. Until an external review is published, the wallet shows lineage in amber as “Lineage checks out · your own node awaiting external review”, never as “Verified”. Checked through a light server it says “your provider” instead, and the specification (WAKE §8.1) forbids presenting a provider’s word as more. Budget: $61 400 [https://zecboat.com](https://zecboat.com) ```auto ``` ---
**Author:** ![George](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@George](https://forum.zcashcommunity.com/u/George)\ **Post date:** [October 14, 2026, 3:11pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/2 "2026-10-14T15:11:32Z")
Thanks for following back up with us. You believed by September you would have a working wallet, things look good on your site. How would an insurer or anyone underwriting a claim check that a certificate they’re shown is the insurer’s original and not a copy? ---
**Author:** ![kworks](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@kworks](https://forum.zcashcommunity.com/u/kworks)\ **Post date:** [October 16, 2026, 4:25pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/3 "2026-10-16T16:25:33Z")
Hi @George, thanks for your groups interest. There is a lot of opportunity for Layer two zcash shielded assets and I think your interested in certificates is smart. To try and answer your question: Any user holding a L2 zsa can view the assets meta data, click on the asset in the wallet and you will see a Lineage dropdown option it will show the assets Lineage checks, which are: Lineage checks out, appears only when every check passes. All four lines have to hold, against the chain: a) the proofs verify; b) each ρ is the previous note’s nullifier; c) every anchor is a real tree root; d) the line ends at the issuer’s genesis output. A copy made with the same memo can’t produce that line, because it doesn’t descend from the genesis output. > **[Send a shielded asset · 0.7.1 - Zecboat](https://zecboat.com/videos/send-shielded-asset-0-7-1)** > > Send a shielded asset · 0.7.1 — a 2:40 Zecboat walkthrough. Video time: 0:40 - Shows the assets Linage checks Minute: 2:09 In the this vide: Send a Shielded Asset you can see the transaction completed all four checks. ![lineage_checks_out_lading_arrow](https://global.discourse-cdn.com/zcash/original/3X/6/e/6e70a249dcdafc2548e4e94fb0523b82a413edac.png) If you have any additional questions, I would be happy to help Thanks ---
**Author:** ![Frank43](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frank43](https://forum.zcashcommunity.com/u/Frank43)\ **Post date:** [October 19, 2026, 8:23pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/4 "2026-10-19T20:23:21Z")
If a group or a user wanted post card collection how should they approach zecboat? Could I receive a L2 zsa? u1sw5eftzzc79hpgleglyydy9g9dzah0knqvqzz7cuve6679fgaaynrr649r7z7jny3uqjdfax8quw0a377n6duq5tujf6z3rpq3zkdrrfcgpf9mcmwsqkruxh2el97vh33x0ygqqdsf6q2dvfhmvkn5tcag05w93pnpc5yyzcgjhwm8kdlh6jvpavkfqk8desdnk58uwyvnfss927745 ---
**Author:** ![kworks](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@kworks](https://forum.zcashcommunity.com/u/kworks)\ **Post date:** [October 21, 2026, 7:58pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/5 "2026-10-21T19:58:06Z")
Hi @Frank43, Yes, a postcard from the Lagos collection has been sent to the address you posted. Open it in Zecboat 0.7.1, click the asset, and the Lineage dropdown will show the four checks running against the chain. On your question about a group or user who wants a collection, that is exactly what we want to hear about. The short version: a. Tell your vision of what the collection should be: the artwork or document, how many units, and who should hold them first. The contact page on [zecboat.com](http://zecboat.com) is the simplest route, or reply here. b. Zecboat mints the genesis outputs and writes the issuer’s closed registry, so every unit traces back to that origin. c. The units are sent to the holders you name. Anyone who later receives one can verify its lineage in the Zecboat wallet, with no server in between. If you say a little about the collection you have in mind, I can answer with specifics. Thanks ---
**Author:** ![Frank43](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frank43](https://forum.zcashcommunity.com/u/Frank43)\ **Post date:** [October 22, 2026, 7:02pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/6 "2026-10-22T19:02:20Z")
Yes, Fantastic. creating demand for a new digital product is hard! The post card is a geniune and limited which can be checked by me th user. I am happy, so happy I wanted to publicly annouce regardless of this grant I have agreed to purchase a number of collections for what I believe is a new zcash product. Zecboat wallet shows wake is working. Support Agreed ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [October 23, 2026, 6:23am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/7 "2026-10-23T06:23:17Z")
“Layer-2 ZSAs” “L2 ZSAs” _What_ L2 ZSAs? ZSAs are NOT operational on mainnet, not even testnet! They are not included in NU7! They aren’t even expected to be deployed at all this year! Where are people asking for this, and more importantly, HOW ARE THEY RECEIVING ZSAs ON A MAINNET ADDRESS. Is this sockpuppetting? @Shawn EDIT: Okay, so apparently this is a custom emulation of a ZSA, which is being sold to third parties as a “Layer 2 ZSA” with no actual value, but as @Frank43 thinks, is a real “collection”. Is this not false advertising? ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [October 23, 2026, 6:27am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/8 "2026-10-23T06:27:42Z")
Why do you think it is a “new Zcash product”? Zcash, Zcash Foundation, or the Zcash chain does not sponsor nor endorse this “layer 2 ZSA” nor the Zecboat wallet. Buy this at your own risk. You are only supporting @kworks, NOT Zcash. ---
**Author:** ![kworks](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@kworks](https://forum.zcashcommunity.com/u/kworks)\ **Post date:** [October 23, 2026, 6:43am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/9 "2026-10-23T06:43:29Z")
Hi @strahncryptography, have you taken the time to explore some great information sources to help with your hesiitations about Layer two zcash shielded assets. I’ve provided some useful links for you and anyone interested: [Collections - Zecboat](https://zecboat.com/collection) (live on zcash mainnet blockchain layer two zcash shielded assets) [Send a shielded asset · 0.7.1 - Zecboat Video Guides](https://zecboat.com/videos/send-shielded-asset-0-7-1) (live mainnet node sending a layer two zcash shielded asset) [Lineage: Wake and Knotline - Zecboat](https://zecboat.com/wake) ( documentation about the innovation of the core of this grant, which is a custom halo2 circuit) [The Zecboat Registry - Zecboat](https://zecboat.com/registry) (documentation about users ability to view on zcash mainnet chain limited supply) [What is an L2 ZSA? - Zecboat Learn](https://zecboat.com/guide/what-is-l2-zsa) (documentation for users learning about layer two zcash shielded assets) Thanks for your interest and even more important your time. ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [October 23, 2026, 7:52am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/10 "2026-10-23T07:52:33Z")
Look, I understand HOW it works, my concern is how are you already advertising it, apparently as a Zcash-endorsed product, WITHOUT an audit or anything similar? ---
**Author:** ![artkor](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/artkor/32/28573_2.png) [@artkor](https://forum.zcashcommunity.com/u/artkor)\ **Post date:** [October 23, 2026, 11:37am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/11 "2026-10-23T11:37:29Z")
Hello @kworks! I have a simple question. Hypothetically, if the community decided to move the Cypherpunk Zero collection to ZecBoat, how reliable and secure would it be as an NFT platform? What guarantees would NFT holders have regarding ownership and transfers, especially if ZecBoat itself stopped operating or being maintained? ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [October 23, 2026, 11:48am UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/12 "2026-10-23T11:48:19Z")
Based on my technical review, as for security, it would be PRETTY secure. The issue is anonymity. NFT transfer would be painfully obvious, occupy a TON of block space, and more importantly, the second issue being an eclipse attack. ZEC has private transfers, so someone else having the same “NFT” cannot be revealed to you unless they choose to, this is the fatal flaw of ZSAs too with respect to fungibility. So you can never establish that you TRULY own a given note unless a secondary arbiter intakes the IVK of the sender and verify that they truly sent you the NFT. It would rely on off-chain indexers. As for how lineage passes, the Git link in the website for source code is broken, so I cannot comment on that for now. I will review it once @kworks provides that. ---
**Author:** ![kworks](https://avatars.discourse-cdn.com/v4/letter/k/c67d28/32.png) [@kworks](https://forum.zcashcommunity.com/u/kworks)\ **Post date:** [October 23, 2026, 7:47pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/13 "2026-10-23T19:47:45Z")
Hi @artkor, If zecboat disappears? the units are ordinary zcash shielded notes, spendable from any wallet that holds the seed. The collection’s manifest, issuer key and closed supply are etched on the zcash chain, and every transfer carries its lineage proof in the transfer itself. Verification runs against the chain, through your own node or a lightwalletd you decide. [zecboat.com](http://zecboat.com) serves the artwork and the wallet checks it by hash, so any host that has the files will do; the IPFS originals (ipfs://QmR5nncezRKzArYmHckb4XdWoe2NRmEVEybiaVThsPuVHD/.png) stay pinned as provenance, and an IPFS fetch path can be added if the community wants it. The wallet and the circuit are MIT [GitHub - zecboat/zecboat · GitHub](https://github.com/zecboat/zecboat) and [GitHub - zecboat/zmap-wake · GitHub](https://github.com/zecboat/zmap-wake). ownership: you own a unit the way you own zec, by holding the spending key of the note that carries it. What Wake adds is proof of which note that is. zcash consensus already says every spent note has exactly one successor, so when a unit is sent to you the transfer carries a chain of proofs from the issuance to the note in your wallet, one per hop, and your wallet checks it against the chain. No second copy can exist, there is no indexer in the path, and nobody has to hand over a viewing key. What it does not prove is the future: that you have not spent it since, or who you are. Those are the same limits zec has, and the spec says so in its own wordz. What is not there yet is the external review of Wake-v1. The wallet says so on every lineage result, and that review is what this grant funds. cypherpunk zero: a token cannot leave ethereum, so a move is a re-issuance on zcash. Thecollection is one verified ERC-721 contract (0x3e86d6cf041b719c575f57050697c115f0a53758), 10,000 tokens, with metadata and artwork on IPFS: tokenURI gives the metadata folder, the metadata names the PNG, three content hashes cover the whole set. That is a good fit, because a zecboat asset is identified by the SHA-256 of its image bytes, not by a URL. Re-issuance would follow, snapshot of holders at a chosen block, each holder signs a message from their ethereum address naming a zcash address, the 10,000 PNGs are pulled from IPFS and each unit is minted with the ethereum token id as its unit number and the image hash in its description, so anyone can walk token id, tokenURI, image, hash and land on the zcash asset. The registry is closed and the three IPFS hashes recorded in the manifest as provenance. the ethereum side is retired so one set is canonical. That decision is the community’s and rights holders. thanks for your interest. ---
**Author:** ![ZCG](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/zcg/32/33712_2.png) [@ZCG](https://forum.zcashcommunity.com/u/ZCG)\ **Post date:** [October 25, 2026, 12:29pm UTC](https://forum.zcashcommunity.com/t/zecboat-com-wake-v1-custom-halo-2-circuit-for-note-lineage/58166/14 "2026-10-25T12:29:15Z")
Thank you for the application. The committee voted not to approve this proposal on October 23. Members’ reasoning is in the minutes: [Zcash Community Grants Meeting Minutes 10/23/2026](https://forum.zcashcommunity.com/t/zcash-community-grants-meeting-minutes-10-23-2026/58488)