Skip to content

core: fullnode set 11 (feat/cs11-revendor 60a7d03) for chain 22 and v0.8.7 - #14

Merged
dendisuhubdy merged 2 commits into
mainfrom
feat/cs11-chain22
Nov 19, 2026
Merged

dendisuhubdy merged 2 commits into
mainfrom
feat/cs11-chain22

Conversation

@dendisuhubdy

Copy link
Copy Markdown
Member

Moves the wallet onto zkVM constraint set 11, the build in fullnode PR #194 (feat/cs11-revendor 60a7d031, circuits 76a48dca), for the chain-22 cut and v0.8.7. Chain cut: this core proves nothing chain 21 accepts. Do not merge before the cut gates; merge order is below.

What moved

  • core/vendor/fullnode → 60a7d031 (via core/scripts/vendor-fullnode.sh); CHAIN_BUILD 60a7d03; lockfiles (path crates 0.8.6).
  • Set-11 pins in the tests: hc_bundle 00782b22…141e, hc_auth 8373994c…6078, bundle_gas_limit 22 527 (was 20 479).
  • DEFAULT_CHAIN_ID 22: core, UI fallback, Android Prefs, iOS Settings fallback.
  • msauth fixtures re-copied from the vendored randprotocol-msig (#194 regenerated them), plus every test pinning their values: fingerprints, policy fingerprint SSJG-ERXD-74B6-SS8Z / last four SS8Z, recipient, shares, signing message. Covers wallet-core, ui, iOS and Android.
  • ui/lib/rpc-methods.js: rand_getBlockContext and rand_getBeacon (the vendored node now dispatches them; the wallet does not call them).
  • e2e harness: --bundle-gas-limit 22527, --chain-id 22.
  • node-integration.yml: FULLNODE_TAG is empty until v0.8.7 is tagged. Meanwhile real-node builds rand-node/rand-prover from the vendored fullnode, because no release verifies set 11 yet. Set v0.8.7 at the tag.
  • No wallet version bump. The convention keeps wallet versions apart from fleet snapshot tags (README); a wallet release on this core is a separate decision.

Tests (build droplet, Rust 1.98.1)

Run Result
core: cargo test --release 151 + 8 + 4 passed, 2 ignored
vendored randprotocol-msig tests ok
ui/test/**/*.test.mjs 1137 / 1137
web/wallet/test/core.integration.test.mjs ok
scripts/e2e-node.sh vs rand-node/rand-prover built from fullnode 60a7d031 (fullnode clients.yml wallet-e2e steps) 29 / 29, including the real-proof send

Not run here: iOS/Android unit tests, desktop cargo test (needs webkit), e2e-msauth.sh, prover.e2e / withdraw.e2e.

fullnode #194's wallet-e2e

clients.yml takes the clients branch named like the fullnode PR's head branch (feat/cs11-revendor) when one exists, otherwise clients main. It pins no rev. So one of these:

  1. merge this PR first, then re-run #194's clients workflow; or
  2. push this head as clients branch feat/cs11-revendor too, and #194's job picks it up on re-run.

Follow-ups

  • Mobile: a one-time 21 → 22 saved-chain migration, like the 20 → 21 one.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo

…chain 22) for v0.8.7

The wallet core moves to the set-11 build fullnode PR #194 runs: new Poseidon2
round constants (Grain), so every note commitment, nullifier, scan key, root and
genesis hash moves; hc_bundle 00782b22..., hc_auth 8373994c..., hc_auth_multisig
41db73c5...; bundle_gas_limit 22 527 (was 20 479). A node on this build refuses
every chain 14-21 genesis, so this core is chain-22-only.

- core/vendor/fullnode at 60a7d031 (vendor-fullnode.sh); CHAIN_BUILD 60a7d03 and
  its doc; Cargo.lock path-crate versions 0.8.6.
- DEFAULT_CHAIN_ID 22 (core, UI fallback, Android Prefs, iOS Settings fallback,
  the Live* iOS tests); the 20->21 mobile migrations are unchanged (a saved 21 is
  not yet moved to 22).
- wallet-core tests: the set-11 hcs, 22 527, chain 22; ProgramStateConfig's new
  reference_block_window field in the ledger fixture.
- msauth fixtures (ui/test/fixtures/msauth) re-copied from the vendored
  randprotocol-msig (regenerated on #194), and every test that pins their
  fingerprints, policy fingerprint, last four (SS8Z), address, shares and
  signing message follows (wallet-core, ui, iOS, Android).
- ui/lib/rpc-methods.js: rand_getBlockContext and rand_getBeacon, which the
  vendored node now dispatches (unused by the wallet).
- e2e harness: --bundle-gas-limit 22527, chain id 22 (node, sections, prover,
  withdraw, msauth devnet).
- node-integration.yml: FULLNODE_TAG empty until v0.8.7 is tagged; the
  real-node job then builds rand-node/rand-prover from the vendored fullnode
  (no release verifies set 11 yet).

Build droplet, Rust 1.98.1: core cargo test --release 151 + 8 + 4 passed,
2 ignored; vendored randprotocol-msig tests ok; ui 1137/1137; web core
integration ok; scripts/e2e-node.sh against rand-node/rand-prover built from
fullnode 60a7d031: 29/29, including the real-proof send.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
@codecov

codecov Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@dendisuhubdy
dendisuhubdy merged commit 2f80ad5 into main Nov 19, 2026
4 checks passed
dendisuhubdy added a commit that referenced this pull request Nov 21, 2026
…last four (#20)

#14 moved the msauth fixture's fingerprint to SSJG-ERXD-74B6-SS8Z but left the typed confirmations
on the old last four (AAK3: "a-ak3", "aak", "a a k 3", " AA-K3 "), so three unit tests failed —
found building the v0.8.7 Android release locally (release.yml does not run them). The app is
unchanged; 195/195 tests pass.


Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8

Co-authored-by: Claude Opus 5.5 <[email protected]>
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