Skip to content

v0.2.0-rc2: zecd 0.8.1, legacy Orchard spends work again - #13

Merged
emersonian merged 2 commits into
mainfrom
be/0.2.0-rc2
Sep 30, 2026
Merged

emersonian merged 2 commits into
mainfrom
be/0.2.0-rc2

Conversation

@emersonian

Copy link
Copy Markdown
Contributor

Release candidate 2 for v0.2.0. Not tagged yet.

v0.2.0-rc1 cannot send or write from a database whose funds sit in the legacy Orchard pool: every attempt fails with Orchard proof generation failed: Prover(ProofFailed(InvalidInstances)) and broadcasts nothing. That covers funds received before NU6.3 activated and change that older software, zkv v0.1.0 included, kept in the Orchard pool afterwards. The cause was in the wallet engine: zecd 0.8.0 proved such spends with the NU6.2 circuit's key, which the prover refuses after NU6.3.

Checked locally: fmt, clippy, 466 tests, a --features desktop build and clippy, MSRV 1.91, cargo deny, rustdoc, the Zakura graph check and cargo publish --dry-run.

- zecd 0.8.0's PCZT send path proved the Orchard-pool bundle with the NU6.2
  circuit's key, which the prover refuses after NU6.3
  (Prover(ProofFailed(InvalidInstances))). Databases carried over from zkv
  v0.1.0 hold such notes, so v0.2.0-rc1 could not send or write from them.
- 0.8.1 proves under the circuit the consensus branch names. No zkv source
  change; the lockfile moves zecd's entry alone.
@emersonian
emersonian merged commit 12e269c into main Sep 30, 2026
18 checks passed
@emersonian
emersonian deleted the be/0.2.0-rc2 branch September 30, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant