AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.
A bug in rippled 3.4.1 misclassifies rotated signing keys as untrusted, temporarily lowering vote counts and thresholds until node restarts.
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.
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. At the time of writing, $XRP traded at $1.40.
Sources
- Amendment voting drops validators that rotate their signing key from votes and threshold (Version: 3.4.1) — Primary document (discovered)
- fix: Key amendment votes and laggards by NodeID so signing key rotations keep counting by dangell7 · Pull Request #8540 · XRPLF/rippled — Primary document (discovered)
Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.
Top comments (0)