Mark the MultiSig demo historical: It and its seven shipped scripts run on halted zcashd. - #1995
Merged
zksquirrel merged 2 commits intoAug 27, 2026
Merged
Conversation
…lted zcashd zcashd reached its automatic End-of-Support halt on 18 July 2026. The page opened with "This demo requires zcashd", and six of the seven scripts shipped alongside it shell out to zcash-cli — 12 invocations in total. The page is curated for translation, so 18 translated copies carried the same dead instructions. A mechanical port is not available: the scripts are built on the raw-transaction and wallet RPCs (createrawtransaction, signrawtransaction, createmultisig, dumpprivkey) that zcashd deprecated, and Zallet replaces those with methods operating on PCZTs rather than raw transaction hex. The page, all seven scripts and all 18 translations now carry the same status notice and point at FROST & Threshold Custody, the Ywallet FROST demo, and the Zebra/Zallet migration guide. Scripts are functionally untouched; only comments were added.
check-invariants requires that a changed translation carry a changed manifest entry. The status notice was added to all 18 locales without recording the pass, so manifest-invariants failed. Each entry's tool field now carries a +zcashd-halt-notice suffix. edited stays false deliberately: flipping it would remove these pages from automated sync permanently, which is wrong for a notice that should be re-translated normally on the next sync.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MultiSig demo and all seven of its shipped scripts run on zcashd, which halted a month ago
site/guides/multisigdemo/MultiSigDemo.mdopened with "This demo requires zcashd" on line 3. zcashd reached its automatic End-of-Support halt on 18 July 2026, so nobody can complete the guide.It isn't only the prose. Seven
.shscripts ship alongside the page, and six of them shell out tozcash-cli; 12 invocations in total acrosscreateMultiSig.sh,createMultiSigTX.sh,getPubkey.sh,sendMultiSignedTX.sh,signMultiSigTX.shandtxDetails.sh. Line 81 still told readers to runzcash-cli dumpprivkey "t-addr". The page is curated for translation (translation/curated-pages.txtline 194), so 18 translated copies carried the same dead instructions. The route is live:https://zechub.wiki/guides/multisigdemo/multi-sig-demoreturns 200 today.Why marked historical rather than ported
A mechanical port isn't available. The scripts are built on zcashd's raw-transaction and wallet RPCs;
createrawtransaction,signrawtransaction,createmultisig,dumpprivkey. zcashd deprecated the raw-transaction family before the halt, and the deprecation notice states that Zallet will instead provide new RPC methods operating on PCZTs ([zcash/wallet#99](zcash/zallet#99)). Zallet is also still in beta, with many zcashd methods not yet ported. There is no target runtime that accepts these scripts as written, so porting them would mean inventing a workflow rather than documenting one.The maintained path for multi-party custody is already documented in this repo, which made the second option straightforward.
What changed
The page carries a status notice directly under the H1, following the pattern established by the Akash zcashd guide. Line 3 now states plainly that zcashd halted on 18 July 2026 and that nothing below can be completed against the live chain. The
dumpprivkeyinstruction is annotated in place.All seven scripts carry a matching header comment after the shebang: what halted, when, why a port isn't mechanical, and where to go instead.
displayQR.shgets an accurate variant; it only callsqrencode, so its header says the demo it belongs to no longer runs rather than claiming the script itself fails. All seven passbash -n.All 18 translations carry the same notice in their own language, so no locale is left presenting the walkthrough as current.
Readers are pointed at [FROST & Threshold Custody](/zcash-tech/frost-threshold-custody), which already contains a direct comparison with transparent multisig, the working [Ywallet FROST demo](/guides/frostdemo/ywallet-frost-demo), and the [migration guide to Zebra and Zallet](/guides/migration-guide-zcashd-to-zebrad-zallet). All three routes return 200 as of today.
Checks
protected-terms --basepasses; no multisigdemo file appears in its warnings. Every protected term introduced by the notice (zcashd,Zallet,Zebra,FROST,Ywallet,Zcash) is present verbatim in all 18 translations.frontmatter-paritypasses for 3654 translated pages.manifest-invariantspasses: 203 curated pages, 18 locales.bash -npasses on all seven scripts;git diff --checkis clean.The Akan (
ak) and Ewe (ee) renderings are the least confident of the eighteen and would benefit from a native speaker's eye. Every other locale reads cleanly. The scripts are left functionally untouched; only comments were added; so the historical record stays exact.