RougeChain node release 1.6.7 — AMM_INTEGRITY on mainnet at block 260 (2026-10)
Mandatory for every mainnet node before mainnet block 260. On testnet nothing changes: AMM_INTEGRITY has been active there since block 1440, and a testnet node on this release validates and produces exactly as on 1.6.6.
What changed
- AMM_INTEGRITY activates on mainnet at height 260 (
upgrade_schedule.amm_integrityis260on mainnet and1440on testnet). From that block, pool transactions (create_pool,add_liquidity,remove_liquidity,swap) apply all-or-nothing: one that cannot take effect changes nothing, pays no fee and does not make the block invalid; swap routes are validated; a pair has one pool; amounts use checked integer arithmetic; the fee of a token-to-XRGE swap is counted as collected. See the upgrade schedule. - A mainnet node on an older release cannot follow the chain past the first block at or above 260 whose pool transactions the old and the new rules judge differently. Installing this release and restarting is enough to catch up.
quantum-vault-daemon --versionreports1.6.7. TherougechainCLI is unchanged (1.3.0).
Everything in release 1.6.6 is included. Below block 260 the mainnet rules are unchanged, and this binary replays mainnet history from block 1 to the same state root as 1.6.6.
Production binary
| Item | Value |
|---|---|
| Binary | quantum-vault-daemon |
| sha256 | e9b4fbf188e28ac3d963f35b28589442d2062890508c47c0b403bbab74aa1626 |
| Size | 29,405,112 bytes |
| Source | quantum-vault c64c90c; public rougechain-node |
| Toolchain | rustc 1.94.0 (4a4ef493e 2026-03-02), x86_64-unknown-linux-gnu |
| Download | https://api.rougechain.io/releases/quantum-vault-daemon-amm-mainnet-260-c64c90c |
| CLI | rougechain 1.3.0, rougechain-c64c90c, sha256 0df5a526a120eeb12ac77a5a86b6b448bbdf80b371c63db0a4c1427ef22f6870 |
Built twice from clean; the two builds were byte-identical. The release is described by a manifest signed with the release keys (Signed releases).
Upgrade
Nodes installed with the one-line installer and auto-update install this release by themselves (node and CLI). Otherwise:
curl -fLo /tmp/quantum-vault-daemon https://api.rougechain.io/releases/quantum-vault-daemon-amm-mainnet-260-c64c90c
echo "e9b4fbf188e28ac3d963f35b28589442d2062890508c47c0b403bbab74aa1626 /tmp/quantum-vault-daemon" | sha256sum -c
systemctl cat rougechain-validator | grep ExecStart # the first path is the binary your node runs
BIN=/path/from/ExecStart/quantum-vault-daemon # set this to that path
sudo systemctl stop rougechain-validator
sudo cp -p "$BIN" "$BIN.pre-1.6.7" && sudo install -m 755 /tmp/quantum-vault-daemon "$BIN"
sudo systemctl start rougechain-validator
Check after the restart: the node follows the chain as before, "$BIN" --version prints
quantum-vault-daemon 1.6.7, and curl -s localhost:5100/api/stats | jq .upgrade_schedule.amm_integrity
prints 260 on mainnet and 1440 on testnet.
To go back (mainnet before block 260 only), stop the node, restore the .pre-1.6.7 binary and
start it again.