← All insights
GRANTZcash Forum · Zecbit

ZecBit: proposal for ZSA-based NFT infrastructure

After minting 10 unique assets in one transaction on the ZSA testnet, ZecBit is requesting funding to build a metadata standard, an indexer and shielded payment tools.

ZecBit posted a ZSA (Zcash Shielded Assets) based NFT infrastructure proposal on the forum, applying to Zcash Community Grants for $48,000. The grant would fund releasing the metadata standard, indexer and shielded payment tools that ZSA apps need but the ecosystem does not yet have. On August 29, it minted 10 unique ZSAs in a single transaction on the public ZSA testnet; the transaction was confirmed at height 251, and proof generation took about 3 seconds on a regular CPU. It has already built the surrounding marketplace layers, including a catalog, a minting studio and a verifier.

The core problem is that there is no standard for wallets to display ZSAs meaningfully. ZIP 227 records only a 32-byte hash of the asset description on-chain and warns wallets not to show the raw description as a trusted name, because anyone can put a name like "Official Wrapped ZEC" in it. The ZIP anticipates a petname system or a trust registry as the solution but does not define one. Without a standard, each wallet would invent its own conventions, causing fragmentation and room for phishing using asset names.

The proposed ZMD-1 lets anyone verify the binding of an asset to its metadata through hashes, with no registry users have to trust. The minimal form is zmd1|<collection>|<index>, and the full form adds a manifest CID and a content hash. In the full form the asset ID indirectly commits to metadata such as artwork and attributes. The manifest is canonicalized with JCS (RFC 8785) and then hashed. The indexer derives asset IDs by scanning issuance bundles without any viewing key, so different operators get the same catalog.

The grant supports three things. First is the standalone ZMD-1 specification with a reference resolver for wallet integration. Second is an open-source indexer. Third is shielded payment receiving, which includes lightwalletd block scanning, trial decryption with incoming viewing keys, memo tag matching, confirmation and reorg handling, and a review queue for unmatched payments, and the payment path will also get an external security review. All three components will be released under permissive licenses, and the marketplace itself is not covered. The budget is $34,000 for compensation and $14,000 for service costs, with one full-time maintainer working for six months.

The author is also clear about the limits. ZSA is not yet on mainnet and is not included in NU7, and everything currently runs on testnet. ZIP 226/227 are drafts, but because the asset ID is derived deterministically from the issuer key and the description hash, they expect that if this approach is kept, the same IDs can be reproduced on mainnet without bridges or wrapping. Also, because ZIP 228 is a draft with no activation schedule, atomic swaps are not possible, so during a purchase the market briefly holds funds in escrow, and this will be stated on the purchase screen and in the spec.

This summary is based on the original; check the original for exact details.