How it works and what can go wrong
This bridge is a beta. It moves real money between the XRP Ledger and XRPL EVM, and some things can go wrong. This page says how it works, where everything is held, what it costs, and what to do if a transfer gets stuck. Read it before you bridge anything you would mind losing.
- Step 1: Bridging in
You send your tokens to the bridge's lock account on the XRP Ledger, with a flat fee in XRP.
- Step 2: Approval by operators
The operators watch the ledger. Once enough of them agree, the transfer goes ahead.
- Step 3: Arrival
The same amount is created as an ERC-20 token on XRPL EVM, in your wallet.
Going back works the other way: you burn the ERC-20 on XRPL EVM and pay a flat exit fee in XRP with it, and the operators send the tokens to the XRP Ledger address you named.
How it works
Bridging in. You send your tokens to the bridge's lock account on the XRP Ledger, together with a flat fee in XRP. The bridge's operators watch the ledger, and once enough of them agree, the same amount is created as an ERC-20 token on XRPL EVM, in your wallet.
Bridging back. You burn the ERC-20 on XRPL EVM and pay a flat exit fee in XRP with it. The operators then send the tokens from the lock account to the XRP Ledger address you named.
Nothing is ever taken from your tokens: the fees are flat amounts of XRP, and what arrives is what you sent (less only the issuer's own transfer fee, where the issuer charges one).
Who holds the tokens
Every token that is bridged in is held in one account on the XRP Ledger, the lock account. It sends when … of its … operator keys sign together; during the beta Blume also holds the account's own key. Each operator runs one node and holds one key. The ERC-20s on XRPL EVM are created and burned by the minter contract, which only accepts instructions signed by … of the same … operators.
Who runs the nodes today
The bridge has … nodes, and any … of them can act. Blume runs all of them for now. So for now you are trusting Blume to run it honestly and to keep its keys safe: if Blume's keys, or the machines they live on, were lost, stolen or misused, the bridged tokens could be lost with them. The plan is to add independent operators over time; this page will say so when that happens.
Limits
A token can have a limit on how much of it the bridge will hold at once. The table below shows each token's limit right now; "none" means whatever is bridged is taken. With no limit, the more that is bridged, the more is at stake if something goes wrong, and the bridge is new, so bridge only what you could stand to lose. A token listed later starts with no deposits until an operator opens it (it can still be bridged back), and an operator can set or lift any token's limit at any time. If a deposit would go over a limit, it is not minted, and your tokens and fee are sent back.
Reading the limits from the bridge…
What it costs
On top of these you pay the XRP Ledger's own small network fee and, on XRPL EVM, gas. A token's issuer may also charge its own fee on every transfer of the token; the bridge shows it before you sign and does not take it. The fees the bridge collects are paid out every day: 70% to the people who run the nodes and 30% to Blume's treasury.
If a transfer gets stuck
Start with Your transfers. It lists everything the bridge knows about your wallets, whether or not the window you started it in is still open.
- Your tokens arrived at the bridge but the fee was not paid. Nothing is minted. You can pay the fee to finish, or pay … to get your tokens back. Nothing expires and nothing is returned for you.
- A release was refused by the XRP Ledger (usually the destination has no trust line for the token). The bridge keeps trying for about a day. Fix the destination and the next try goes through; if it never does, the tokens are minted back to your EVM wallet.
- The deposit was over the token's limit. It is not minted, and your tokens and fee go back to your XRP Ledger wallet.
- You started a transfer and never paid it. It expires on its own, usually within the hour, and nothing is sent.
- The bridge is paused. In an emergency the operators can pause new deposits, and this site can pause new transfers. Transfers already under way carry on.
If something still looks wrong after an hour or two, write to support@blumefi.com with the transfer id (it is in the transfer's details) and the transaction hashes.
No insurance, and other risks
Nothing here is insured or guaranteed. Do not bridge more than you could afford to lose.
- The tokens on XRPL EVM are claims on the lock account. They are worth what the tokens in it are worth. If the lock account is emptied, by lost keys, stolen keys or a bug, the ERC-20s stop being backed.
- The code is new. The minter contract and the software the operators run can have bugs. The contract has no owner and cannot be upgraded, so a flaw means a new contract and a migration, which takes time.
- Issuers decide things about their own tokens. An issuer can freeze the lock account's hold on its token, which pauses that token, and it can change its own transfer fee. The bridge refuses tokens whose issuer can take them back from holders.
- The networks and wallets can fail. The XRP Ledger, XRPL EVM, Xaman and your EVM wallet can be down or slow. A transfer then waits; it does not disappear.
- Amounts finer than the ledger can carry are rounded down. The XRP Ledger carries 15 significant digits, so a smaller remainder of a burn stays in the lock account as extra backing.
Reaching Blume
Email support@blumefi.com, or find Blume on X and Discord. Never send anyone your seed or secret key: nobody at Blume will ask for it.