--- title: "XRPL Core Developers Address Bug Dropping Rotated Validators From Amendment Votes" description: "A bug in rippled 3.4.1 misclassifies rotated signing keys as untrusted, temporarily lowering vote counts and thresholds until node restarts." url: https://basisdesk.news/news/xrpl-bug-amendment-voting-signing-key-rotation published: 2026-10-09T04:26:34.105Z modified: 2026-10-09T04:26:34.105Z section: Tech & Protocols author: Basis Desk Newsroom (AI-generated, source-verified) sentiment: neutral tickers: [XRP] tags: [XRPL, rippled, validators, governance, consensus] license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice. --- # XRPL Core Developers Address Bug Dropping Rotated Validators From Amendment Votes A bug in rippled 3.4.1 misclassifies rotated signing keys as untrusted, temporarily lowering vote counts and thresholds until node restarts. ## At a glance - **What happened:** XRPL developers identified a bug in rippled 3.4.1 that drops validators from amendment vote tallies following signing key rotations and opened a pull request to resolve it. - **Why it matters:** The issue temporarily lowers the total quorum denominator and vote counts on un-restarted nodes, potentially shifting the timeline required to reach an amendment majority. - **Who is affected:** XRP Ledger validator operators running long-lived rippled nodes and validators rotating their signing keys. - **What's next:** Review and merging of pull request #8540 into the rippled codebase ahead of an official release. - **Primary source:** [Amendment voting drops validators that rotate their signing key from votes and threshold (Version: 3.4.1)](https://github.com/XRPLF/rippled/issues/8534) — github.com ## Key points - A bug in rippled 3.4.1 drops trusted validators from amendment counts after signing key rotations. - Mainnet voting nodes saw denominators slip from 35 to 33, lowering the required amendment threshold from 28 to 26. - XRPLF pull request #8540 proposes keying amendment votes and laggard tracking by stable NodeIDs rather than signing keys. ## Editorial remark - **Context:** The flaw originated in rippled version 2.0.0 via issue #4410, where internal amendment tables were keyed to ephemeral signing keys instead of persistent master identity keys. - **Impact:** Validators and UNL nodes on XRPL running long uptimes undercount active votes, artificially altering the quorum threshold required to lock in new network amendments. - **Watch:** Review and merge progress on rippled pull request #8540, followed by a patched software release for XRPL validator operators. A bug in the XRP Ledger reference implementation `rippled` has been causing long-running proposing validators to drop trusted validators from feature amendment tallies after ephemeral signing key rotations [1]. The issue, identified in `rippled` version 3.4.1, temporarily reduces both the counted votes and the total denominator required to activate protocol amendments [1]. According to an issue opened on the XRPLF GitHub repository, nodes track amendment votes using validator signing keys rather than persistent master public keys [1]. While a validator's master identity remains on the Unique Node List (UNL), rotating its ephemeral key does not trigger an internal UNL update [1]. Consequently, observing nodes treat the new key as untrusted, relying on cached votes from the previous key for roughly 24 hours before removing the validator from vote counts and lowering the voting threshold entirely [1]. The behavior was observed passively on the XRPL mainnet, where the active denominator slipped from 35 to 33 trusted validations during voting on the `BatchV1_1` amendment [1]. ## Impact on Protocol Governance The defect alters threshold mathematics in both directions: dropping a rotated validator that favors a proposal delays majority status, while dropping an opposing validator can inadvertently trigger early consensus [1]. Although maintainers noted that no amendment pass-or-fail outcome has differed on mainnet so far, explorer data showed affected validators reporting a lowered 26-vote requirement instead of the standard 28-of-35 quorum [1]. Developer dangell7 submitted Pull Request #8540 on Oct. 8, 2026, to address the fault [2]. The proposed fix transitions amendment voting and consensus laggard tracking from signing keys to stable validator NodeIDs derived from master keys, ensuring that key rotations retain active voting power without requiring node reboots [2]. As developers review the patch, long-running validator operators can restore full UNL counts by restarting their nodes [1]. This development follows broader ecosystem growth, including initiatives like [CSD BR partnering with Ripple to mirror financial assets on the XRP Ledger](https://basisdesk.news/news/csd-br-ripple-xrp-ledger-brazil-tokenization). At the time of writing, $XRP traded at $1.40. ## Sources 1. [Amendment voting drops validators that rotate their signing key from votes and threshold (Version: 3.4.1)](https://github.com/XRPLF/rippled/issues/8534) — github.com, 2026-10-09 2. [fix: Key amendment votes and laggards by NodeID so signing key rotations keep counting by dangell7 · Pull Request #8540 · XRPLF/rippled](https://github.com/XRPLF/rippled/pull/8540) — github.com, 2026-10-09 --- Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai