Repository navigation
core: fullnode set 11 (feat/cs11-revendor 60a7d03) for chain 22 and v0.8.7 - #14
Merged
Merged
Conversation
…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 Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…d on the test chain) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
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]>
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
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.
Moves the wallet onto zkVM constraint set 11, the build in fullnode PR #194 (
feat/cs11-revendor60a7d031, circuits76a48dca), 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(viacore/scripts/vendor-fullnode.sh);CHAIN_BUILD60a7d03; lockfiles (path crates 0.8.6).hc_bundle00782b22…141e,hc_auth8373994c…6078,bundle_gas_limit22 527 (was 20 479).DEFAULT_CHAIN_ID22: core, UI fallback, AndroidPrefs, iOSSettingsfallback.randprotocol-msig(#194 regenerated them), plus every test pinning their values: fingerprints, policy fingerprintSSJG-ERXD-74B6-SS8Z/ last fourSS8Z, recipient, shares, signing message. Covers wallet-core, ui, iOS and Android.ui/lib/rpc-methods.js:rand_getBlockContextandrand_getBeacon(the vendored node now dispatches them; the wallet does not call them).--bundle-gas-limit 22527,--chain-id 22.node-integration.yml:FULLNODE_TAGis empty until v0.8.7 is tagged. Meanwhile real-node buildsrand-node/rand-proverfrom the vendored fullnode, because no release verifies set 11 yet. Setv0.8.7at the tag.Tests (build droplet, Rust 1.98.1)
core: cargo test --releaserandprotocol-msigtestsui/test/**/*.test.mjsweb/wallet/test/core.integration.test.mjsscripts/e2e-node.shvs rand-node/rand-prover built from fullnode60a7d031(fullnodeclients.ymlwallet-e2e steps)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.ymltakes the clients branch named like the fullnode PR's head branch (feat/cs11-revendor) when one exists, otherwise clientsmain. It pins no rev. So one of these:clientsworkflow; orfeat/cs11-revendortoo, and #194's job picks it up on re-run.Follow-ups
🤖 Generated with Claude Code
https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo