$XRP Security Patch Delayed Until November, Only 26 of 35 Validators Support It; Countdown Resets
A critical security patch for the XRP Ledger has been delayed until November after the number of supporting validators dropped to 26 out of 35, triggering a reset of the countdown timer.
Developments:
The number of supporting validators has since climbed back up to 31.
However, because the two-week countdown period had to be recalculated, the patch missed its original deployment window.
This is a rather delicate situation. The vulnerability in question could potentially allow the XRP total supply limit to be bypassed a highly serious issue. Notably, ZachXBT has criticized the $250,000 bounty for this discovery as being far too low.
While the delay caused by a lack of validator consensus is not a sign of operational failure (the mechanism is actually functioning as intended), it does highlight how decentralized decision-making can be slow when responding to a crisis.
A tally of 26 out of 35 validators falls below the threshold required to activate the patch. Resetting the countdown is consistent with the established protocol, but it effectively means the vulnerability will persist for several more weeks.
If the vulnerability is truly this critical, why did only 26 validators support the patch? Are they unaware of the full extent of the risk, or is there another reason?
Decentralized governance comes at a price: slower processes. On the bright side, it remains transparent.
The XRPL Foundation has confirmed that no additional XRP has been minted, and the vulnerability has already been addressed in version 3.4.1 though its activation on the mainnet remains pending.
XRPL has delayed the security patch until November what are your thoughts on how this is being handled?
News is for reference, not investment advice. Please read carefully before making a decision.
A critical security patch for the XRP Ledger has been delayed until November after the number of supporting validators dropped to 26 out of 35, triggering a reset of the countdown timer.
Developments:
The number of supporting validators has since climbed back up to 31.
However, because the two-week countdown period had to be recalculated, the patch missed its original deployment window.
This is a rather delicate situation. The vulnerability in question could potentially allow the XRP total supply limit to be bypassed a highly serious issue. Notably, ZachXBT has criticized the $250,000 bounty for this discovery as being far too low.
While the delay caused by a lack of validator consensus is not a sign of operational failure (the mechanism is actually functioning as intended), it does highlight how decentralized decision-making can be slow when responding to a crisis.
A tally of 26 out of 35 validators falls below the threshold required to activate the patch. Resetting the countdown is consistent with the established protocol, but it effectively means the vulnerability will persist for several more weeks.
If the vulnerability is truly this critical, why did only 26 validators support the patch? Are they unaware of the full extent of the risk, or is there another reason?
Decentralized governance comes at a price: slower processes. On the bright side, it remains transparent.
The XRPL Foundation has confirmed that no additional XRP has been minted, and the vulnerability has already been addressed in version 3.4.1 though its activation on the mainnet remains pending.
XRPL has delayed the security patch until November what are your thoughts on how this is being handled?
News is for reference, not investment advice. Please read carefully before making a decision.
