Proposal to move Shielded Assets to Ironwood
Zecoshi posted a discussion proposal to retarget the Orchard-based draft ZIPs 226 and 227 to the Ironwood pool and assign them to a network upgrade.
Zecoshi posted a discussion proposal for using Zcash Shielded Assets (ZSA) beyond payments, to protect records such as licenses, certifications, memberships and ownership. The core claim is that holding and transfers can stay private while the total issued supply can be proven publicly.
As background, the author noted that ZIP 226 (transfer and burn) and ZIP 227 (issuance) are in Draft status and have not been assigned to any network upgrade. Both drafts are based on the Orchard protocol, but after NU6.3 no new value can enter the Orchard pool, and its successor pool, Ironwood, was introduced in NU6.3.
The proposal explains that Ironwood notes can be recovered through a future Recovery Protocol under ZIP 2005 (Final), but that this does not mean they are safe against quantum attacks. Lean 4 formal verification of Ironwood is in progress, and the proposal is to bring asset logic into the scope of that verification.
Under ZIP 226, note commitments of custom assets are indistinguishable from those of ZEC, so a new asset inherits the anonymity set of the whole pool. Asset transfer fees are paid in ZEC following ZIP 317. On the other hand, ZIP 227 issuance notes are not encrypted, so the first recipient is public, and the proposal recommends issuing sensitive records to the issuer's own address first and then transferring them.
The proposal makes four recommendations: assign ZSA to a specific network upgrade, rewrite ZIPs 226 and 227 to target Ironwood, extend Lean formal verification to the asset circuits, and confirm that all Ironwood asset notes are recoverable under ZIP 2005. It also acknowledged that a new transaction format may be needed.
This summary is based on the original; check the original for exact details.