What happened
XRP Ledger is preparing a fix for the new lending mechanism, but its launch still depends on 10 missing validator votes.
Why it matters
The patch addresses a problem in a function that has not yet received permission to launch, so its technical readiness and validator approval are not yet aligned.
XRP Ledger developers have prepared a second patch to fix the code of the new unsecured lending mechanism. According to CoinDesk and Decrypt, the update is planned to be deployed on Friday.
The lending mechanism itself has not yet been approved: it lacks 10 validator votes. This means the patch partially touches a function that has not yet received the necessary approval.
For XRP Ledger, the next key signal is the outcome of the validator vote and the actual deployment of the patch. The available information is provided as metadata from sources, so details of the bug and deployment conditions remain unknown.
Confirmed facts
- Validators are preparing a patch to fix an error in the XRP Ledger code.
- The patch is planned to be launched on Friday.
- The fix relates to the new unsecured lending mechanism of the XRP Ledger.
- The lending mechanism has not yet been approved and is short of 10 validator votes.
- Decrypt reports a second patch for this mechanism published by XRP developers.
Context
This concerns the XRP Ledger lending function, which is still awaiting validator approval. The sources in the provided package are available only as metadata and brief synopses, not as full-text materials.
What remains unknown
- What exact bug has been found in the code?
- Will the patch be activated on Friday?
- When will the lending mechanism receive the missing 10 votes?
- Will the patch alter the parameters or architecture of the lending function?
Editorial context
Confidence: medium
An expected consequence is that the launch of the lending function will depend on two separate stages: patch deployment and validator approvals. The next observable signal is patch activation or a change in the number of votes. Substantial uncertainty remains around the error's content and timing of mechanism approval.