The Ledger
Zecoshi Proposes Shielded Assets for Zcash’s Ironwood Pool
A Zcash community forum proposal would retarget draft shielded-asset rules from Orchard to Ironwood and seek a place for them in a named network upgrade. It envisions private asset holdings and transfers with publicly verifiable supply, but the proposal remains under discussion.

A proposal, not a network change
A discussion proposal from Zecoshi would retarget Zcash’s draft shielded-asset rules from the Orchard pool to Ironwood and ask that the feature be assigned to a named network upgrade. Posted to the Zcash Community Forum on November 13, the document is marked “Proposal for discussion”; it does not describe an approved or scheduled change.
The proposal frames an asset as a record of entitlement, such as a licence, credential, title, membership, ticket or access right, rather than a new coin or currency. Its stated aim is to let holders keep asset balances and transfers private while leaving total supply publicly provable.
Draft rules need retargeting
The document identifies ZIP 226, covering asset transfers and burns, and ZIP 227, covering issuance, as the existing drafts. Both are marked Draft in the Zcash Improvement Proposals pages. The proposal says they were written for Orchard and are not scheduled for a network upgrade; it argues they should instead target Ironwood, the shielded pool introduced in NU6.3.
Zecoshi recommends assigning the feature to an upgrade, revising the two ZIPs for Ironwood, extending the pool’s Lean formal-verification work to cover asset logic, and confirming that asset notes can use the recovery path described in ZIP 2005. The proposal says the Ironwood repository describes its formal verification as in progress, and it acknowledges that the work is unfinished.
Records beyond payments
The proposed use cases include professional licences, identity and age credentials, memberships, access rights, ownership titles, tickets and software licences. The post argues these records could be held as shielded notes rather than in a readable register. It presents the ability to verify supply publicly while concealing individual holdings as a feature of the design.
Issuance would remain transparent under the current draft, according to the proposal: the issuer key, issued amounts and an asset’s global balance would be public. The author says transfers could keep asset identifiers and amounts private. ZIP 227 likewise describes its issuance mechanism as transparent and says it is intended to enable public tracking of asset supply.
Open technical questions
The proposal says retargeting likely needs a new transaction format, because version 6 is now used for Ironwood. It also stresses that Ironwood is not quantum secure: the recovery path is not a claim of immunity to quantum adversaries. Formal verification remains in progress, and the proposal says asset logic would need to be included in that effort before activation.
It also notes limits in the current issuance design. Directly minting an asset to its eventual holder would reveal that recipient at issuance, so the proposal suggests issuers mint to their own address and distribute assets through shielded transfers. Shielding would not protect stolen keys or identity information kept off-chain, the post says.
Sources
- Original source Zcash Community Forum forum.zcashcommunity.com
Other pages read
- Zcash Improvement Proposals · page 1 zips.z.cash
- Zcash Improvement Proposals · page 2 zips.z.cash
Related stories
- Zcash ZIP Proposes 50,000-ZEC Donation, Redirects 8% Grants Stream
- Zcash Member Proposes Limits on Grant-Recipient ZCAP Votes
- Zcash draft ZIP would cap both grant treasuries quarterly
- Zcash forum post calls for miner input in NU7.1 poll assessment
- Zcash Vote Preserves Four-Year Halvings as Zakura Tests 25-Second Blocks