The XRP Ledger Foundation said on October 28 that Flare has joined the recommended validator list it publishes. In its post on X, the Foundation said Flare shares the ledger’s core values, takes part in governance and contributes to the wider ecosystem. Flare replied within minutes. It said it’s now a trusted XRPL validator and called itself “one more operator for a ledger that runs on many.” About two minutes after its first post, the Foundation added that Anodos Finance came off the list at its own request, as Anodos retires its XRPL validator by the end of the month.
XRPL’s documentation defines a unique node list as the validators a server trusts not to collude. The default configuration uses two such lists, one from the Foundation and one from Ripple, and the docs say they’re typically very similar or even identical. On October 29, XRPScan listed 174 validators, yet only 35 sat on the UNL. That’s a small roster. The table showed a validator at xrpl-verification.flare.network among them, with anodos.finance outside the UNL. Coverage in September and early October also counted 35 trusted validators, so the change looks like a swap, not an expansion. The timing lines up with Anodos shutting its node down.
Why one seat matters
Seats matter because of how the ledger changes its rules. An amendment has to keep support from more than 80% of trusted validators for two weeks before it activates, the XRPL docs say. PermissionDelegationV1_1 cleared that mark and went live on October 8. Others haven’t yet. XRPScan’s amendment tracker, checked the same day, showed LendingProtocolV1_1, which arrived with xrpld 3.4.0, at 18 of 34 validators in its count, with SingleAssetVault at 20 and ConfidentialTransfer at 19. At those margins, each operator’s vote is worth watching.
Flare’s stake in XRP DeFi
Flare is an EVM Layer 1 whose XRP strategy centers on FXRP, a token that XRP holders can mint one to one for use in DeFi. FXRP went live on mainnet on September 24, 2025. Flare’s one-year update put minted FXRP at roughly 145 million, according to a late-September report. In July, co-founder and CEO Hugo Philion presented a six-month roadmap meant to make Flare a programmable layer for the XRPL and to link XRP holdings with decentralized finance apps, Börse Express reported.
Flare’s roadmap already touches the amendment queue. In September, CoinTurk reported that Philion outlined a plan to let users borrow RLUSD against XRP through Flare smart accounts, with the stablecoin delivered on the XRPL itself. The plan, per the report, depends on validators approving the Permission Delegation amendment. That amendment has since activated. The validators Flare is joining have already voted on a feature its plans need.
Who is affected and what’s still open
Operators who follow the Foundation’s list feel the change first. Their servers weigh votes from this roster. Anyone tracking the lending and vault amendments is watching the same count, now with one new name among the voters. None of the three posts ties the move to FXRP or any other Flare product.
The ledger itself is changing. Votes don’t always keep pace. XRPL has spent 2026 shipping DeFi tools, from lending code to delegated permissions, and every one needed a validator vote. In July, BlockchainReporter reported that a new release had majority validator support while a separate security amendment trailed on its own vote. That’s why the roster matters more as the ledger takes on DeFi. XRPScan’s table already mixes universities, exchanges such as Bitso and Bitrue, and ecosystem firms like GateHub and Bithomp. Flare adds a Layer 1 network’s own validator to that group.
Plenty is still unclear. The Foundation’s posts don’t say when servers will pick up the change, which checks Flare passed or how long its validator has been running. The XRPL docs say each publisher can set its own criteria, though typical ones include a year of high uptime, domain verification and a separate physical location, and operators may interview candidates before listing them. Whether Ripple’s list will follow isn’t known, since the Foundation’s post covers only its own. Neither does Flare’s reply say how it will vote on the pending proposals. And a single vote can’t carry an amendment that needs support from more than 80% of the list.
The next signals are concrete: a note from the Foundation on when the change reaches servers, whether Ripple’s list adds Flare, and where Flare’s validator lands on the lending and vault votes if those proposals near the 80% line.
