XRP Ledger Operations

XRP Ledger Infrastructure and Software updates. Community Discord:

[XRP Ledger Operations @XRPLOperations]

The XRP Ledger is no longer experiencing those occasional slower ledger closes following the publication of the recommended xrpld configuration.

We are continuing to prepare a dot release for the community to address the behavior observed.

[XRP Ledger Operations @XRPLOperations]

We've begun rolling out a recommended xrpld config change to hub, validator and node operators to address the issue for now.

In parallel, we're testing fixes for a point release that will address the root cause.

We'll continue updating the community as we progress.

[XRP Ledger Operations @XRPLOperations]

We've begun rolling out a recommended xrpld config change to hub, validator and node operators to address the issue for now.

In parallel, we're testing fixes for a point release that will address the root cause.

We'll continue updating the community as we progress.

[XRP Ledger Operations @XRPLOperations]

This is still the case, and you may occasionally observe slower-than-usual ledger close times on the XRP Ledger.

Outside of this, closing times are normal.

We're aware of the issue and are finalizing a fix release targeting it as soon as possible.

[XRP Ledger Operations @XRPLOperations]

This is still the case, and you may occasionally observe slower-than-usual ledger close times on the XRP Ledger.

Outside of this, closing times are normal.

We're aware of the issue and are finalizing a fix release targeting it as soon as possible.

[XRP Ledger Operations @XRPLOperations]

Some ledger closings on the XRP Ledger are currently slower than usual, and ledgers can occasionally take longer to close. Outside of this closing times are normal.

We have been actively investigating this and working on a fix since earlier today.

We'll keep you updated!

[XRP Ledger Operations @XRPLOperations]

Some ledger closings on the XRP Ledger are currently slower than usual, and ledgers can occasionally take longer to close. Outside of this closing times are normal.

We have been actively investigating this and working on a fix since earlier today.

We'll keep you updated!

[XRP Ledger Operations @XRPLOperations]

Welcome, on @XRP !

[XRP @XRP]

hello, world.

It’s about time.

[XRP Ledger Operations @XRPLOperations]

XRP Ledger version 3.4.1 is now the minimum required version after the recent amendments were activated.

This release patched critical parts of the XRP Ledger.

The vulnerability report can be found here:
https://t.co/sYIwuDomjY
Public release notes:
https://t.co/JqX4UYDDg6

[Mayukha Vadari @msvadari]

https://t.co/2kHknL4hv5

[XRP Ledger Operations @XRPLOperations]

xrpld 3.4.1 is being released with a Batch fix and stability improvements.

We’re asking validators and node operators to upgrade as soon as possible. There has been no impact to mainnet, and no loss of funds.

There is also a new fix amendment, fixBatchV1_2, which addresses a minor issue with Batch that does not pose a risk to funds.

The amendment is marked as Default Yes. Both Batch and the fix amendment are in the activation period and set to activate in 2 weeks. A detailed technical report will be shared after the fix amendment has been activated.

[XRP Ledger Operations @XRPLOperations]

XRP Ledger version 3.4.0 is now available ✅

New amendments for voting:

- Lending Protocol v1.1 - closed-ended vaults and cash-basis accounting.
- fix Cleanup - bundled fixes.

Performance and Stability:

- Online delete now pauses on ledger history gaps, so nodes stay closer to the tip.
- Peer protocol hardening and faster MPT freeze checks.

Packages have moved to https://t.co/OXwbB1hnFY with an XRPLF signing key. Nodes on 3.3.0 or earlier must update their repo config.

Release blog post:
https://t.co/Geywxbyy5X

[XRP Ledger Operations @XRPLOperations]

Formal Verification for the XRP Ledger Lending Protocol.

The Lending Protocol (XLS-66) and Single Asset Vaults (XLS-65) are not smart contracts. They are native financial logic inside xrpld.

FV raises assurance above ordinary testing. Specify the behavior that must always hold, prove it in a machine-checked model, and keep that model aligned with the production code.

In depth thread why @CommonPrefix picked Lean 4 to perform FV on XRPL.

ICYMI: Formal Verification is part of the new security approach to amendments - https://t.co/nIAkrifM9H

[Common Prefix @CommonPrefix]

We're formally verifying the XRP Ledger Lending Protocol, going beyond the usual testing, using methods that mathematically prove the protocol can never be drained, become insolvent, or behave outside its intended rules.

In this thread we cover how we settled on Lean 4. 1/6 🧵

[⚡️Kris Dangerfield @krisdangerfield]

Run an XRP Ledger node/validator? I need just a few minutes of your experience. Fill in the operator survey here👇 and help shape the new XRPL node documentation for https://t.co/GBM6LF6S0e aimed at builders and enterprises.
https://t.co/50V1foIG1F

[Mayukha Vadari @msvadari]

The Batch V1.1 amendment shipped in xrpld 3.3.0 and is now up for voting.

After the v1.0 signature bug was caught in February (pre-Mainnet, no funds at risk), we rebuilt it: root-cause fix, 4 senior reviewers, a Sherlock attackathon, and audits from Halborn and Common Prefix. We also fixed a few other bugs our new AI red-teaming efforts caught along the way.

What changed and why it's ready: https://t.co/atPZWvxQvS

Atomic transactions on the XRPL, no smart contracts needed. Try it on Devnet today.

[XRP Ledger Operations @XRPLOperations]

https://t.co/jbIxkCPxv3

[XRP Ledger Operations @XRPLOperations]

Formal Verification is raising the bar for security in the blockchain space.

The XRP Ledger formal verification already led to increased security and protocol hardening.

[Common Prefix @CommonPrefix]

Excited about the work with @RippleXDev on formally verifying the XRP Ledger. More on the technical details behind this effort. 🧵 1/6

[XRP Ledger Operations @XRPLOperations]

Lending v1.1 ships in XRPL 3.4.0

Join us on why it matters, what's new, and what it unlocks.

• @angell_denis CTO, XRPLF
• @ja_akinyele Head of Engineering, RippleX
• @jazzicoop Head of Product, RippleX
• @v_tumas Senior Software Engineer, RippleX
https://t.co/jbIxkCPxv3

[Mayukha Vadari @msvadari]

The same technology that just let Claude formalize Fermat's Last Theorem is also being used to formally verify the XRP Ledger. We're working with @CommonPrefix to prove, mathematically, that XRPL's most critical parts do exactly what we expect them to do.
https://t.co/LTGimlaCWk

[XRP Ledger Operations @XRPLOperations]

@cantinasecurity Read more about:

- Cantina security review https://t.co/SPYJt1Qpyj

- QA test
https://t.co/npdaIJJaqP

[XRP Ledger Operations @XRPLOperations]

Permission Delegation on the XRP Ledger has passed an independent security review by @cantinasecurity and the XRPL quality assurance test suite.

All findings were fixed in v1.1 and verified by Cantina, and the QA team found no regressions across 5,088 tests.

[XRP Ledger Foundation @XRPLF]

The refreshed https://t.co/DeErclx2sX is now live.

New design. Clearer paths for institutions, developers, community members, and newcomers to learn about the XRP ecosystem.

Find developer resources and explore use cases across payments, tokenization, trading, and more.

See what's new: https://t.co/xRQyBZobHK

[⚡️Kris Dangerfield @krisdangerfield]

XRPLF (Node docs update)!

We're progressing with the development of the new node operator documentation for https://t.co/6dOgnlmXsX (XRPLF project) and want it grounded in how people actually run nodes, not how the defaults say they should.

If you run any kind of XRPL node, validator, hub, full history, stock, anything, we'd like 15 minutes of your time on a short questionnaire.

Tell us your setup and your story in your own words. Every contributor gets a named shout-out in the published documentation (or stays anonymous if you prefer). No sensitive details wanted: we deliberately don't ask about IPs, ports or topology.

If you run infra and are prepared to contribute around 15-20 mins of your time, please reach out to me on @X