The XRP Ledger Foundation has added Flare to its recommended validator list and removed Anodos Finance at the company’s request as Anodos prepares to retire its validator. The change affects which validators the Foundation recommends. It does not automatically reconfigure every XRPL server.
- A snapshot showed the Foundation’s and Ripple’s published lists each contained the same 35 validator keys.
- Both lists included a validator manifest with Flare’s domain, but the snapshot does not show when or why Ripple’s list changed.
- Flare’s FXRP activity began before the list update; no new product launch, payment, or grant was announced with it.
What changed on the recommended list?
The Foundation announced Flare’s inclusion, saying: We welcome Flare to the recommended XRP Ledger validator list, and pointing to the project’s alignment with XRPL’s core values and its participation in governance.
The Foundation also removed Anodos Finance at the company’s request, thanking it for its contributions and collaboration with the XRP ecosystem. Anodos was preparing to shut down its validator that month and planned to retire it by the end of October. It did not give an exact shutdown date.
A snapshot comparison of the Foundation’s and Ripple’s published lists found 35 shared validator keys, with none unique to either list. Both payloads also included a validator manifest containing the domain xrpl-verification.flare.network. A validator key identifies a validator. A manifest links information, such as a domain, to that key.
The snapshot shows that Flare’s validator appeared on both publishers’ lists when they were checked. It does not show when Ripple’s list came to match the Foundation’s, whether Ripple made a separate announcement, or why its list changed. The Foundation announced Flare’s addition. The matching snapshot is not evidence of a separate Ripple endorsement.
A recommendation does not reconfigure the network
A validator helps XRPL servers agree on transaction ordering. Each server’s Unique Node List (UNL) is the set of validators whose votes it considers during consensus. Operators choose their own lists, so a validator’s presence on a publisher’s recommended list does not automatically make it trusted by every server. A discussion of an XRPL validator issue shows why those choices matter.
XRPL documentation says the default server configuration uses recommended lists from both the Foundation and Ripple. If a validator appears on both lists, a server that combines them counts it only once. That default does not show which configurations individual operators use or how many rely on Flare’s validator.
Overlap between servers’ trusted validators matters because their votes help establish agreement on validated ledgers. But overlap alone does not guarantee consensus. Servers also need to meet the protocol’s quorum requirements. A list publisher recommends validators, but publishing a list does not mean it routinely validates transactions on their behalf.
The XRPL FAQ says recommended-list selection considers past performance, verified identities, and responsible IT practices. Those criteria describe what publishers say they look for. The list change itself does not provide a public performance record or guarantee future reliability.
According to the XRPL FAQ, validators do not earn XRP rewards, and running one does not require holding XRP. That does not make operating one free: hosting and maintenance take resources. The Foundation did not disclose a payment or grant to Flare, and no payment or grant was announced alongside its inclusion.
Flare’s FXRP work predates the list change
Flare’s validator recommendation is separate from its work to make XRP usable in applications on other networks. Flare activated FXRP on mainnet in September 2025, initially using version 1.2 of its FAssets protocol and setting a first-week minting cap of 5 million FXRP.
Flare describes FXRP as a one-to-one representation of XRP, secured by an overcollateralized system involving independent agents and Flare’s data protocols. That work was already underway before the Foundation added Flare to its recommended list. The Foundation announced no FXRP launch, payment, or grant alongside the validator change.
Key questions and answers
-
What does a recommended validator list mean?
It tells XRPL server operators which validators a publisher recommends they consider. Operators choose their own trusted lists, so a recommendation does not automatically add a validator to every server’s UNL.
-
Did the Foundation’s list match Ripple’s?
Yes. A snapshot showed that both lists contained the same 35 validator keys, including one associated with Flare’s validator domain. It does not show when Ripple’s list changed or whether Ripple separately announced the addition.
-
Was Flare paid or given a grant for inclusion?
No payment or grant was announced alongside the change. XRPL validators do not receive XRP rewards, though operating one still involves hosting and maintenance costs.
-
Did FXRP launch with the validator-list change?
No. FXRP had been active on Flare mainnet since September 2025. The Foundation announced no new FXRP product alongside the list update.
The update adds Flare to the validators recommended by the Foundation as Anodos prepares to exit. It is a recommendation, not a network-wide configuration change or a guarantee of validator performance.
Related developments include tokenized U.S. Treasuries on the XRP Ledger and Mastercard’s RLUSD tests on XRPL.
