28 verifiers in the Axelar network sign every bridge operation between XRPL and the XRPL EVM Sidechain. 19 must agree.
Snapshot updated 1d ago· live updates stream below
Scope
What we watch:
the Axelar bridge's gateway account on the XRP Ledger — the vault-like account holding bridged funds — and every successful change to its keyholder list (who can move the money).
Where the data comes from:
Ripple's public servers, polled at a respectful pace.
What's permanently missing:
our history starts 2026-06-08. Earlier keyholder changes happened but weren't captured and cannot be recovered.
What this page is NOT:
other XRPL bridges (FXRP, Squid, future Wormhole NTT) aren't tracked here.
Technical details
Gateway account: rfmS3zqrQrka8wVyhXifEeyTwe8AMz2Yhw
Transactions watched: SignerListSet with result tesSUCCESS.
Query path: account_tx scanned against our own rippled node by the bridge-signer walker, cached to our database. Full methodology →
The XRPL EVM Sidechain bridge runs on Axelar Amplifier — Axelar's framework for
connecting new chains to its interchain network. On the XRPL side, a single
account holds the SignerList that authorizes every bridge operation; that account
is the receiving address for user-initiated bridge transfers and the signing
account for messages relayed back from the Sidechain.
A bridge transfer starts as a regular XRPL Payment transaction sent to
that account, with hex-encoded memos carrying the destination chain, contract,
and ABI-encoded payload. The Axelar network verifies the payment and relays it
to the Sidechain, where the Amplifier gateway approves the message and a relayer
executes the call on the target contract.
The verifiers themselves are Amplifier participants who post a bond
(50,000 AXL on mainnet) and register support for specific chains via an
xrpl-handler binary. The set above is what XRPL mainnet sees today;
the observed quorum sits at roughly two thirds of total signer weight, which is
the safety property — not the verifier count itself. When the set rotates,
it shows up here as a new SignerListSet transaction on the gateway
account, recorded in the timeline above.