Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,12 @@ invariants, and known traps.

## Project memory (state as of 2026-11-08)

### Constraint set 11 re-vendored (issue #166 step 7; 2026-11-20, branch `feat/cs11-revendor`, PR open, NOT merged)
### Constraint set 11 re-vendored (issue #166 step 7; 2026-11-20, #194 merged as `94b2c15c`; v0.8.7)

**v0.8.7** is this build: version bump on `release/v0.8.7` (from main `e79070a7`, after #197's
`cutover-fleet-chain22.sh`), release notes `docs/releases/v0.8.7.md`. Not tagged, signed or
rolled as of 2026-11-20; the chain-22 genesis hash and its `CHAIN_CONSTRAINT_SETS` row are
`PLACEHOLDER-…` there until the cut.

`CIRCUITS_PIN` **`41d64acd`** (circuits main: set 11 landed at `76a48dca`, "Constraint set 11:
Grain constants, declared poseidon2 height, quotient layout, versioned rVM key"; then #27, the EVM
Expand Down
32 changes: 32 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,38 @@ stopped at v0.4 until 2026-09-30, when the entries v0.5 to v0.6.7 were written f

## Unreleased

Nothing yet.

## v0.8.7 — PLACEHOLDER-TAG-DATE (chain 22, **a chain cut**: constraint set 11; a set-11 node refuses every chain 14–21 genesis, so this release is never rolled onto chain 21)

The release notes — the set-11 gas change as a governance record, the chain-22 cut, the operator
upgrade steps and the rollback — are [`docs/releases/v0.8.7.md`](docs/releases/v0.8.7.md).
Assets: `rand-node`, `rand`, `rand-prover`, `msauth-vk-production.bin` (set 11, `168d79a8…71b3`)
and the four `perp-vk-production-t18-*.bin` state-proof keys, with `SHA256SUMS` (eight lines;
seven of them are the files the fleet installs) and the owner's `SHA256SUMS.sig`.

Release (no node change beyond the version):

- **The chain-22 cut re-derives every shielded address under set 11** (#199). The same spend
key has a different `rand1…` address under set 11 (`pk = H_PK(nk)` is a Poseidon2 output).
`cut-chain22-genesis.sh` now takes `WALLET22` (the v0.8.7 `rand`) next to chain 21's
`WALLET`, and tells them apart by a probe key. It re-derives every alloc, zUSD carry, faucet
recipient and validator payout from a held key file (or a recorded `given=` address and
fingerprint), and refuses any address chain 21 knew. The fee recipient has no chain-21 default.
- **The fleet switch from chain 21 to chain 22: `deploy/cutover-fleet-chain22.sh`** (#197),
derived from chain 21's cutover. The build is v0.8.7 at constraint set 11, so `switch` keeps
v0.8.6's `rand-node`, `rand` and chain 21's msauth blob as `*.pre-c22` and `rollback` restores
all three. Seven signed files are staged and checked on every host (`rand-node`, `rand`, the
set-11 msauth blob, the four perps keys). New phases `beacon-init` (each validator makes its own
seed on its own host; the seed never leaves it) and `beacon-collect` (`BEACON_TSV`);
`check-beacon-seed.sh` runs at `stop`, `switch`, `start` and `wait`. 25 validators (archive2
dropped), quorum 17. `stop` refuses without `CONFIRM_HALT_CHAIN21=halt-chain-21-for-<first 8 hex
of the pushed genesis hash>`. `verify` needs the `CHAIN_CONSTRAINT_SETS` row. Every changing
phase appends to `deploy/roll-records/v0.8.7-chain22-cutover.record`. `SELFTEST=1` rehearses
the whole cutover against 26 fake hosts (`deploy/rehearse-cutover-fleet-chain22.sh`).
- **Workspace version 0.8.7** (`Cargo.toml`, the seven workspace crates in `Cargo.lock`, the
`rand_getVersion` test).

Perps (**a chain cut, chain 22**; chain 21 unchanged):

- **Chain 22's perps on constraint set 11.** The cut pins the engine at `482215a8…5073` (chain
Expand Down
14 changes: 7 additions & 7 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ members = ["crates/randprotocol-core", "crates/randprotocol-zkvm", "crates/randp
exclude = ["vendor/circuits/evm-core", "vendor/circuits/sbpf-core", "vendor/circuits/dilithium-core"]

[workspace.package]
version = "0.8.6"
version = "0.8.7"
edition = "2021"
license = "GPL-3.0-only"
authors = ["RandProtocol Contributors"]
Expand Down
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -359,6 +359,7 @@ a time.
| v0.7.0 | node-only: the audit v7 addendum (bounded by-hash deferral, header pages capped by reply size, a prover timeout, the wallet's resumable first sync hardened) and the last audit v6 rows (a clean-clone build, an incremental token root, the key-separation schedule); the first workflow-built, signed release | 20 |
| v0.8.0 | chain 21's cut build: constraint set 9 (rVM phase 4's Merkle spans, the MODQ chip), tree aggregation, scan heads, compact blocks, the `fees` section, RPL-3 perps, public and private multisig | 21 |
| v0.8.2 | node-only on chain 21: the audit v10 node, perps and prover-pool fixes (the prover memory gate, the two-member pool pin, threshold release signatures); its consensus rules are genesis-gated to the next cut | 21 |
| v0.8.7 | chain 22's cut build: constraint set 11 (Grain Poseidon2 constants, declared poseidon2 height, rate-¼ quotient layout, versioned rVM keys, cell-count gas: bundle 22 527, auth 1 407, msauth 355 775), EVM block context and the randomness beacon, pinned perps state-proof keys, the 5-of-6 treasury; refuses chains 14–21 ([release notes](docs/releases/v0.8.7.md)) | 22 |

## v0.5: RPL, zUSD and bridge hardening

Expand Down
2 changes: 1 addition & 1 deletion crates/randprotocol-node/src/rpc.rs
Original file line number Diff line number Diff line change
Expand Up @@ -10287,7 +10287,7 @@ pub(crate) mod tests {
// passed happily through v0.2, v0.3 and v0.4 while the field reported 0.1.0 (audit v3,
// PROC-3). The workspace version is bumped with each tag, and this is what notices when it
// is not.
assert_eq!(v["version"], "0.8.6", "bump the workspace version in Cargo.toml with the tag");
assert_eq!(v["version"], "0.8.7", "bump the workspace version in Cargo.toml with the tag");
// The full 40-hex commit, `-dirty` when tracked files differed at build time, or
// "unknown" when neither git nor a `.git-rev` could say — never a short or stale form.
let sha = v["git_sha"].as_str().unwrap();
Expand Down
Loading
Loading