myXRP

myXRP is not XRP and is not affiliated with Ripple.

Contract audited 8 contract audits Live contract match

8 Contract audits completed

14 Flare C-Chain · chainId

On-chain identity

What explorers should list

The token name is myXRP. That is what name() returns on the working contract only: 0x14b9dd90edaaff6527c1b168550b3faa15b9f6af. Symbol myXRP, 6 decimals, official FXRP. Any other Flare contract that returns the same name or symbol is not the working contract. The desk uses only this address.

Official token name: myXRP
Symbol: myXRP
Decimals: 6
Chain: Flare C-Chain · chainId 14
Contract: 0x14b9dd90edaaff6527c1b168550b3faa15b9f6af
Underlying · official FXRP: 0xAd552A648C74D49E10027AB8a618A3ad4901c5bE

The bridge source is published. Open the Flare explorer contract tab or the Sourcify exact match of 30 September 2026, 22:11 UTC. flarescan.com only redirects there; a client that stops on the 301 sees an empty page.

Flare explorer · contract · Sourcify exact match

Official FXRP, 0xAd552A648C74D49E10027AB8a618A3ad4901c5bE, is an EIP-1967 proxy in the Flare FAssets system. The myXRP bridge does not administer that proxy. An upgrade of the implementation, or a pause of FXRP, sits with FAssets and is outside this bridge.

Contract audit

8 contract audits completed

8 contract audits are published — Claude Opus, Claude Sonnet, Grok, GPT, Gemini, Composer, Audit Utility, and Comply Security. An audit lowers bug probability; it does not cancel market, custody, or operational risk.

Claude Opus Contract audit

Claude Sonnet Contract audit

Grok Contract audit

GPT Contract audit

Gemini Contract audit

Composer Contract audit

Audit Utility Contract audit

Comply Security Contract audit

Machine-readable

Same bytes explorers can fetch

/token.json Name, symbol, decimals, chain, contract address Flare explorer Verified source, contract tab Sourcify Exact match, 30 September 2026, 22:11 UTC Security desk Coverage and the 8 contract audits