zscal / PROTOCOL & EVIDENCE
The token is destroyed. The certificate records that event. The mechanism is easier to judge when today's implementation is separated from tomorrow's proposal.
Token amount
Recipient address
Finality & token
Rules & uniqueness
Commit / reveal
Public certificate
Read both chains
Rebuild the ledger
Architecture from the project repository ↗. This redesign does not operate these services.
VERIFIABLE CLAIMS
An inscription existing on a chain does not, by itself, prove the underlying burn is valid.
The website presents a mainnet example. The repository README still says its end-to-end flow is on local Solana and Zcash testnet. This may be outdated documentation; production readiness needs further verification.
Website ↗Repository status ↗ZIP 227 was marked Draft when checked on 21 Sep 2026. It describes an asset issuance protocol; it does not endorse this token or promise this project's conversion.
Read ZIP 227 ↗The original site cites a certificate for 1,500,000 tokens. Its current activity snapshot reports a different 1,000,000-token burn. These are shown separately rather than forced into one counter.
The site describes a forged inscription accepted by the chain but rejected by its application rules. This illustrates why a chain transaction and a valid certificate are not equivalent.
Read the validation rules ↗DEPENDENCIES, NOT DEADLINES
The source design records a burn in transparent Zcash transactions. It does not make the owner's holdings private.
Zcash would need the relevant protocol support. A specification does not provide a reliable activation date.
The project would still need a working, verified conversion implementation and clearly defined asset terms. No fixed redemption value follows from the recorded amount.
TRUST & COST
The burn destroys tokens instead of locking them in a vault. Issuance still depends on correct validation, processing services, indexers, funding and network availability. A non-custodial label does not establish security of the whole system.
The source describes watcher and minter services. Missing fee funding, service outages or chain issues can delay issuance while the Solana burn remains irreversible.
Account for Solana transaction fees, the tokens you destroy, Zcash inscription funding and any launch charges. The original site reports no established certificate market, so an estimated resale value should not be assumed.
Use a self-custodied Zcash transparent address supported by the original flow. Exchange deposit addresses can receive funds without giving you control of an inscription. zscal never requests or generates recovery phrases.
The project requires a real qualifying burn, a unique claim against that burn, and delivery to the recipient named in its memo. The original site says anyone can rebuild the valid set from public data on both chains. This redesign shows source records; it does not run that independent reconstruction.
The project's stated approach is to use inscriptions while waiting for native shielded asset support. A unique inscription can reference one burn, but it does not automatically receive the protocol guarantees of a future native asset.
PRIMARY SOURCES / CHECKED 21 SEP 2026
01Original website↗02Project activity feed↗03Protocol source & documentation↗04ZIP 227 — Issuance of Zcash Shielded Assets↗