Ripple Engineer Questions FXRP Bridge Security as Flare Co-Founder Pushes Back

More than 155 million FXRP have been minted on Flare, representing a substantial amount of XRP (CRYPTO:XRP) on a network separate from the XRP Ledger. That scale makes a recent dispute over FXRP’s security worth watching, after Ripple engineer Neil Hartner questioned the system on September 8, 2026, and Flare co-founder Hugo Philion pushed back by pointing to the protocol’s collateral, escrow and verification mechanisms.

The disagreement centres on what protects XRP once it is represented on Flare, a programmable network built for smart-contract applications. XRP trades around $1.43 on September 9, but the more important question is what holders are relying on when they move their XRP into FXRP.

 What Wrapped XRP Is and How FXRP Works

The XRP Ledger is built primarily for payments and value transfer, while Flare provides a smart-contract environment where assets can be used across decentralised applications. Because native XRP cannot operate directly within Flare’s ecosystem, FXRP provides a representation of XRP that can interact with Flare’s applications while remaining redeemable for the underlying asset.

FXRP is created through Flare’s FAssets system, which uses collateral and other safeguards to support the token’s redemption back into XRP. Agents play a central role in that process by providing collateral and facilitating the underlying XRP transactions, while the protocol’s contracts and verification mechanisms coordinate the minting and redemption of FXRP.

That structure means holding FXRP involves a different set of assumptions from holding XRP directly on the XRP Ledger. An FXRP holder depends on the system to accurately verify the underlying XRP, maintain sufficient collateral and process redemptions when requested, making the security of those mechanisms central to the disagreement between Hartner and Philion.

What Hartner and Philion Disagree About

The disagreement centres on whether FXRP’s security mechanisms can adequately protect the XRP represented on Flare. Ripple engineer Neil Hartner questioned the system’s security assumptions, while Flare co-founder Hugo Philion defended its design by pointing to the collateral, XRPL escrow and verification mechanisms that support FXRP.

FXRP also differs from a conventional wrapped-asset model in which a single custodian holds the underlying asset and issues an equivalent token on another network. Flare’s FAssets system uses agents that provide collateral and facilitate the minting and redemption of FXRP, with additional safeguards intended to protect the system if an agent fails to meet its obligations.

The issue, then, is not whether safeguards exist, but whether they are sufficient to contain the risks involved. Those protections can reduce the consequences of a failure, but they cannot eliminate the underlying technical and operational risks, which is why the security assumptions behind FXRP remain the central point of disagreement.

Why Bridges Keep Getting Attacked

Blockchain bridges have become frequent targets for exploits because they have to move or represent value across networks that were not designed to communicate directly. That creates several points where things can go wrong, including the smart contracts, verification process, custody arrangements or the participants responsible for securing the system. When something fails, the assets represented on the other side can be affected too.

The amount of money involved also matters. The more assets a bridge holds or represents, the greater the potential damage if something goes wrong. That is what makes the FXRP debate relevant beyond Flare: it raises a broader question about how much additional risk users take on when they move an asset from its native network into another blockchain’s ecosystem.

For XRP holders, the choice is relatively simple. Keeping XRP on the XRP Ledger does not require a bridge, while using FXRP means relying on another system to keep the representation secure and make redemptions work as intended.

What XRP Holders Should Ask Before Wrapping Into FXRP

When XRP stays on the XRP Ledger, holders are dealing with the native asset on its own network. Moving XRP into another ecosystem changes that setup, because the holder now has to rely on the system that represents, secures and eventually redeems the asset. That distinction matters even while XRP is performing strongly. XRP is up roughly 40% over the past 30 days but remains down about 24.5% since January 1, while Bitcoin, Ethereum and Solana have also posted strong monthly gains. Those moves show where the market is trading, but they say nothing about the security of FXRP or the system behind it.

For anyone considering FXRP, the important thing is understanding what sits between the token and the XRP it represents. That means looking at how the underlying XRP is secured, how the system is protected against failures and how redemption works if something goes wrong. For FXRP, those details are publicly documented, including its collateral requirements, escrow arrangements and multiple security reviews. That does not make the system risk-free, but it gives holders something concrete to assess before deciding whether the added utility is worth the additional risk.

Contact [email protected] for any questions or corrections.