The ZSA testnet is a distinct public network dedicated to testing ZSA. It is not the regular Zcash testnet. It runs a ZSA-enabled version of Zebra and lightwalletd, with NU 6.2 activated (but not Ironwood). Anyone can issue custom assets, transfer them between shielded addresses, and finalize them, using test funds that have no real value. Addresses use the regtest prefix uregtest1, not the mainnet u1.
The ZSA testnet exists so application developers can build on ZSA and experiment.
That’s the qedit “testnet”. I don’t think it is maintained anymore. Moreover the cli tool was only performing specific transactions (mostly for testing and demos).
still work-in-progress, but the version at QEDIT repo now points to the latest ironwood, in prep for merging (under feature-flag).
SEPERATELY, and for the curious you can checkout thisexperimental wallet derived from tx_tool.
This isn’t a QEDIT release, rather it was a fully implemented experiment, somewhat tested by Fable, to check the ergonomics of a regular wallet cli doing ZSA.
From the README:
Wallet Usage
Once the node is running and the tool is built (see Getting Started), the wallet is operated through subcommands:
# See node connection and wallet state
zcash_tx_tool status
# Show your shielded receiving addresses (unified + raw hex)
zcash_tx_tool addresses
# Issue 1,000,000 units of a new shielded asset to account 0
zcash_tx_tool issue "MY-TOKEN" 1000000
# Send 250,000 units to another wallet's unified address
zcash_tx_tool transfer "MY-TOKEN" 250000 --to uregtest1...
# Burn 50,000 units (provably reduce supply)
zcash_tx_tool burn "MY-TOKEN" 50000
# Permanently close the asset's supply
zcash_tx_tool finalize "MY-TOKEN"
# Balances, notes and known assets
zcash_tx_tool balance
zcash_tx_tool notes
zcash_tx_tool assets
(When running from the repository, prefix with cargo run --release -- or use ./target/release/zcash_tx_tool.)
ZSA will be the first truly decentralized and fully private economy. ZSA will be the first truly decentralized and fully private economy. One question that comes to mind is:
what will determine the shared price of a ZSA token? Since transactions for these assets are completely hidden, there will have to be some kind of oracle to agree on the exchange price, and this will have to be public, right?
Hi @hanh ..quick provenance question about the dedicated public ZSA Testnet.
Could you confirm the exact zcash-shielded-assets/zebra commit SHA or container/image digest currently running behind zsa.methyl.cc?
The live endpoint reports Zebra 5.0.0 / Nu7 and matches the published ZSA genesis exactly. I currently infer commit 6a91831a6a9c18f667f59ab956c9437bf0bb5c5f, but I don’t want to treat that as deployed provenance without confirmation.
Also, if possible: is ZIP-226 assetBurn parsing/validation enabled in that deployed build, or is there an accepted public-testnet burn tx/vector I can reference?
Thanks ..that exact commit is what I needed. I’ll pin 6a91831a6a9c18f667f59ab956c9437bf0bb5c5f and verify the assetBurn handling against that revision locally
