Repository navigation
Releases
ycashd v6.22.0-beta2 (Yellowback)
ycashd v6.22.0-beta2 is a beta for testing, not for production funds. It is ycashd 6.20.0 (the Ycash
rebase onto the Zcash 6.x line) with a proposed Ycash network upgrade, the vault upgrade (consensus branch
ID 0x6d5b7a31), and Ycash Yellowback (YED), the one rule module built on it: lock YEC in a vault to mint
YED (1 YED = 1 US dollar), return the YED to get the YEC back. The vault upgrade and Yellowback are proposed,
not adopted by the Ycash Foundation, and not audited.
No activation height is set on mainnet. On mainnet this build runs as a normal Ycash node. The upgrade is
active only on the fast testnet and on regtest.
The tag v6.22.0-beta1 exists, but its release run failed before any package was published, so this is the
first published beta. The changes below are those since that tag. This release changes no consensus rule of
this node line: every change is in the wallet, the RPCs, the address text and the build.
What changed since beta1
- Send YEC between every address type.
z_sendmanytakes an ECC (s1…), Sapling (ys1…) or
post-quantum from-address and pays any mix of ECC, Sapling and post-quantum recipients. A post-quantum
source spends only its own coins and gets its change back. A transaction with a post-quantum input pays a
fee priced on its size: about 27,000 zat for one SLH-DSA input, 5,500 zat for one FN-DSA-512 input.
vault_locktakes an optional"from"address of any of the three types. - Balances by address type.
z_gettotalbalanceaddstransparent_ecc,transparent_pqand
pq_by_scheme.getwalletinfoaddsbalance_ecc,balance_pq, their unconfirmed figures and
pq_by_scheme.listaddresseshas apqlist, andz_getbalanceandz_validateaddressaccept a
post-quantum address. Existing fields keep their meaning. - The stock sends spend ECC coins only.
sendtoaddress,sendmany,sendfromandfundrawtransaction
never select a post-quantum coin (in beta1 they did). When ECC coins do not cover the amount and the wallet
holds post-quantum coins, the call is refused and says so. Spend post-quantum coins withz_sendmanyfrom
their address. This is the beta2 decision. - Post-quantum addresses show their scheme. The third character names the signature scheme. On mainnet
that issqf…(FN-DSA-512) andsqs…(SLH-DSA) for YEC, andybf…/ybs…for YED. On testnet it is
tqf/tqs/ytf/yts, and on regtestrqf/rqs/yrf/yrs. The earlier form is refused by every
RPC. Keys, scripts and balances are unchanged, and the wallet rewrites its address book once. - RPC contract version 9.
yed_getinfo.rpcversionis 9, andparams.pqAddressVersion/
params.pq.plainAddressVersionare objects keyed by scheme number. lightwalletd-dd and the YEW wallets
require exactly 9. - The other node lines now follow this line's rules. ycash-dd (the 4.5.0 reference line) now rejects
non-canonical Jubjub encodings in Sapling signatures and coinbase outputs at every height (ZIP-216). kogany
now accepts Ycash's block-time bounds (10,800 s past the median time, 14,400 s past the clock). This
line's behaviour is unchanged. - Sapling on the fast testnet for light wallets. The YEW light wallet and
yewdnow build Sapling
transactions on the fast testnet (librustzcash6 carries the fast heights). Before, they refused on
testnet. - Also: a seed-only restore (
-mnemonicfile) finds transparent coins and resumes after an interruption.
Vault transactions no longer leave coins locked until a restart. More guards keep YED from being spent as
plain YEC.getunconfirmedbalanceworks again. The Windows package builds again, andmacos_aarch64is
built onmacos-15.
The full notes, with every changed error string and the table of behaviour changes for existing callers, are
in doc/release-notes/release-notes-6.22.0-beta2.md.
The RPCs are documented in doc/vault-rpc.md and doc/yellowback-rpc.md.
Before you upgrade
- Back up
wallet.dat. At first start this build rewrites the wallet's post-quantum address-book entries
in the new form. An earlier build still sees the keys and coins but loses their labels. - Clients must speak RPC contract version 9.
- Do not leave
-yellowback=0in a configuration file.
Networks
| network | select with | P2P / RPC | vault upgrade | seed (-addnode=) |
|---|---|---|---|---|
| mainnet | (default) | 8833 / 8832 | no activation height | built in |
fast testnet (testnet-yb-fast) |
-testnet -testnetprofile=fast |
18833 / 18832 | active from height 510,400 | fastnet-seed.ycash.team |
slow testnet (testnet-yb-slow) |
-testnet -testnetprofile=slow |
18933 / 18932 | no height yet | slownet-seed.ycash.team |
legacy testnet (testnet-legacy) |
-testnet -testnetprofile=legacy |
19033 / 19032 | never | legacy-seed.ycash.team |
| regtest | -regtest + -nuparams (below) |
18344 / 18832 | at the height you choose | none |
The seed nodes of all three testnets run ycashd 6.22.0-beta2 (/YcashCpp:6.22.0-beta2/). No testnet seed is
compiled in, so name one with -addnode. -testnet without a profile is refused. The slow and legacy
testnets copy Ycash mainnet up to height 3,079,999, so joining them means a mainnet-sized sync.
Qualification
The release candidate was qualified on the tag (rc-qualify run 43425204088, record
rc-qualify-43425204088.json attached to this release): the signed packages, the release train, every
node suite (unit, functional, sanitizers, lockorder, nightly, coverage), every client against the
package (YecWallet, lightwalletd and the light wallets, x402, Hawkeye, the walkthrough), ycash-dd
nodes on the same devnet with identical state hashes, and the launch ceremony rehearsal passed.
One step of the audit job failed for a CI reason, and this release is published with that exception
by the beta2 decision: run on a tag, the audit's cross-line check compared ycash6 with an obsolete
ycash-dd record branch instead of the matching ycash-dd code. Run at this tag's commit against
ycash-dd vault-params/v6.22.0-beta2, the full audit passes (all nine legs, 62 shared files
identical, identical Vault chain parameters), as it did at the same commit in the qualification run
on upgrade/vault (43362159753). The routing is fixed for future tags.
Known limitations
- No mainnet activation height and no YED attestor set on any public network. YED cannot be minted on
the fast testnet with this build. Yellowback is live only on regtest with-yellowbackattestorset.
Sends, balances andvault_lockwork on the fast testnet. z_sendmany'sminconfdefaults to 10. On the fast testnet, which is mined on demand, coins received
fewer than 10 blocks ago need a lowerminconf(for example1).- The
yed_*YEC funding can still spend post-quantum coins: the ECC-only rule covers the stock sends only. - A seed restore does not restore the has-held-YED mark. Restore a wallet that has held YED only on a node
where Yellowback is live. - Wallet encryption is experimental (
-experimentalfeatures -developerencryptwallet). - The macOS binaries are ad-hoc signed and not notarized (see the macOS step below).
ubuntu_18.04_x86_64andmacos_x86_64are built best effort.- The SBOMs (
*.spdx.json) describe the files in each package. They do not list the libraries compiled
into the binaries. gettransactionshows a wrongfee(andamount) for a transaction funded from Sapling: the
shielded value going in is not counted, sofeeis the sum of the transparent outputs (a send of
1 YEC to each of three transparent or post-quantum addresses showsfee3.0). The transaction on
the chain pays the normal fee, and balances, coin selection,listtransactionsand
z_viewtransactionare not affected. This is inherited from upstream zcashd and will be fixed on
both lines in the next release.
Download, verify, run
Packages: ycashd_v6.22.0-beta2_<platform>.tar.gz for linux_x86_64, linux_aarch64 and
macos_aarch64, ycashd_v6.22.0-beta2_windows.zip, and best effort ubuntu_18.04_x86_64 and
macos_x86_64. Each holds ycashd, ycash-cli, ycash-tx, ycashd-wallet-tool and COPYING in a
directory of the same name.
1. Download your package, SHA256SUMS and SHA256SUMS.cosign.bundle (example: Apple silicon):
V=v6.22.0-beta2; P=macos_aarch64 # or linux_x86_64, linux_aarch64, ...
for f in SHA256SUMS SHA256SUMS.cosign.bundle ycashd_${V}_${P}.tar.gz; do
curl -fLO https://github.com/boyfromcave/ycash6/releases/download/$V/$f
done2. Verify. Check the checksum first. Then check that SHA256SUMS was signed by this repository's release
workflow at this tag. Then (optionally) check the package's GitHub build provenance:
sha256sum -c --ignore-missing SHA256SUMS # macOS without sha256sum: shasum -a 256 -c --ignore-missing SHA256SUMS
cosign verify-blob --bundle SHA256SUMS.cosign.bundle \
--certificate-identity https://github.com/boyfromcave/ycash6/.github/workflows/yellowback-release.yml@refs/tags/v6.22.0-beta2 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com SHA256SUMS
gh attestation verify ycashd_${V}_${P}.tar.gz -R boyfromcave/ycash6 \
--source-ref refs/tags/v6.22.0-beta2 \
--signer-workflow boyfromcave/ycash6/.github/workflows/yellowback-release.ymlExpect …: OK for your package, Verified OK from cosign, and exit status 0 from gh attestation verify
(it prints nothing on success when its output is not a terminal). Every package, SBOM and SHA256SUMS itself
carries a provenance attestation. When the Yellowback lead architect has signed the checksums,
SHA256SUMS.minisig is attached too:
minisign -Vm SHA256SUMS -P RWQYr5PFpiPJAigk86vf89bPYrJCXj5tskgRAPRYFsEXyciZo8dveOGQ.
3. Unpack. On macOS,...