Skip to main content
Leading options · 7 ranked from 10 screened

Relayers

Relayers evaluated across what the relayer is authorised to do, and whether you can keep the address, exactly-once execution and stuck-queue recovery, what a stolen API credential can do before anyone notices, and where the gas float sits and how you get it back.

#1 of 7 · published ranking
Coinbase CDP Server Wallets (API-key wallets)
81ChainChoice Score
Why it leads
Best in the pool on credential blast radius (10/10; next 9/10)
Cost
Not priced · No comparable price is published
No provider can pay for a position in this table. The code that computes this order cannot read which links earn us a commission, and every build proves it. Every score below rebuilds from the published criteria.Ranking 2026.08 · 4 criteria · 7 products · same inputs, same order
Personal comparison

Relayers ranked comparison

No comparable price is published; ranking still uses verified product evidence.

RankProviderBest fitScore
1
Coinbase CDP Server Wallets (API-key wallets)A backend API that creates EOAs whose p...Top ranked
What a stolen API credential can do before anyone notices — 10/10Trade-off: CDP does publish replacement semantics — a replaced original "will never land onchain...
81score
Check availability for your countryVisit Coinbase CDP Server Wallets (API-key wallets) · docs.cdp.coinbase.com

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

2
Privy server walletsA REST/SDK service that generates or im...
What the relayer is authorised to do, and whether you can keep the address — 9/10Trade-off: Privy never retries or reprices for you — "The endpoint does not wait for confirmatio...
78score
Check availability for your countryVisit Privy server wallets · docs.privy.io

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

3
Openfort backend walletsOpenfort backend walletsA custodial server-side signer: Openfor...
What the relayer is authorised to do, and whether you can keep the address — 9/10Trade-off: Openfort will submit for you, but it will not help you when submission jams. There is...
75score
Check availability for your countryVisit Openfort backend wallets · openfort.io

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

4
OpenZeppelin RelayerOpenZeppelin RelayerAn AGPL-licensed Rust service a backend...
What the relayer is authorised to do, and whether you can keep the address — 10/10Trade-off: Your server-side guardrail on EVM is two policy fields — a destination allowlist and...
73score
Check availability for your countryVisit OpenZeppelin Relayer · docs.openzeppelin.com

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

Same score, not joint · ordered by weighted total (45.50 against 45.40)
5
Sequence Transactions API (Relayer)Sequence Transactions API (Relayer)A hosted relayer that accepts a signed...
What the relayer is authorised to do, and whether you can keep the address — 9/10Trade-off: Five of the chains this relayer publicly advertises do not exist as endpoints: polygo...
73score
Check availability for your countryVisit Sequence Transactions API (Relayer) · docs.sequence.xyz

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

6
Circle Gas StationCircle Gas StationCircle fronts network fees for transact...
Where the gas float sits and how you get it back — 8/10Trade-off: On EVM you cannot use Gas Station without an ERC-4337 smart contract account — "the P...
71score
Check availability for your countryVisit Circle Gas Station · developers.circle.com

Commission: This provider pays ChainChoice nothing for this link. Disclosure

Crypto products are high risk. Check the provider is authorised where you live before you deposit.

1 more assessed and ranked below — none of them hidden for commercial reasons.
Ranking blindCommercial terms excludedDated primary sources

Ranked on 4 published criteria weighted 32/26/22/20, which set goal alignment — 30 of the 86 points. The rest: regional access 20, evidence depth 18, ease of use 10, institutional trust 8. Profile match is shown in breakdowns but carries no weight.

Audit
Infrastructure
Methodology
2026.09.15
published 2026-09-16
Providers tracked
980+
across 119 categories
Last verified
2026-08-11
newest dated pricing or sentiment read
Named on the roster
2 people
managing directors · 6 automated processes
Decision guide

What matters most before choosing in this category

This page deliberately publishes no cost ranking, and that is the first thing to know about it. Price per transaction and the markup on sponsored gas are already scored on Account Abstraction Infra, and cost per call on RPC & Node Services, so ranking them again here would print the same numbers under a different heading — and in one case contradict them. What is left is the part nobody else asks, because a relayer inverts the usual arrangement: everywhere else on this site the user signs and the vendor forwards, but a relayer holds a key and transacts as your backend, which means its address ends up holding a privileged role inside your own contracts. So start with what that address is allowed to do and whether you can keep it, because an address is wired into contracts as a role grant and a key you cannot export turns leaving into an on-chain re-permissioning exercise. Then read the retry semantics, where this pool is uniformly weak: nobody here scores above 7, because vendors publish the words "nonce management, gas estimation and resubmission" and stop short of saying whether a repriced transaction reuses its nonce. Then check what a leaked API token can actually send, and last, whether the gas you deposit can ever come back out.

What matters most before choosing in this category

This page deliberately publishes no cost ranking, and that is the first thing to know about it. Price per transaction and the markup on sponsored gas are already scored on Account Abstraction Infra, and cost per call on RPC & Node Services, so ranking them again here would print the same numbers under a different heading — and in one case contradict them. What is left is the part nobody else asks, because a relayer inverts the usual arrangement: everywhere else on this site the user signs and the vendor forwards, but a relayer holds a key and transacts as your backend, which means its address ends up holding a privileged role inside your own contracts. So start with what that address is allowed to do and whether you can keep it, because an address is wired into contracts as a role grant and a key you cannot export turns leaving into an on-chain re-permissioning exercise. Then read the retry semantics, where this pool is uniformly weak: nobody here scores above 7, because vendors publish the words "nonce management, gas estimation and resubmission" and stop short of saying whether a repriced transaction reuses its nonce. Then check what a leaked API token can actually send, and last, whether the gas you deposit can ever come back out.

Does the vendor's address become msg.sender inside your contracts, or does it only fund a call your end user signed?
Can you keep the address — import a key, export the one they generated, or point the service at a signer you control?
If a repriced transaction is resubmitted, does it reuse the original nonce, so the intent executes at most once?
What can a stolen API token send before anyone notices — and can that same token delete the limits meant to bound it?
Current editor lead

Expert review and scoring weights

Coinbase CDP Server Wallets (API-key wallets)Data checked Aug 2026
A backend API that creates EOAs whose private keys are generated inside Coinbase's AWS Nitro Enclave TEE, then signs and broadcasts transactions from them on seven EVM mainnets and Solana, with import and export of the raw private key both exposed as REST endpoints.

A backend API that creates EOAs whose private keys are generated inside Coinbase's AWS Nitro Enclave TEE, then signs and broadcasts transactions from them on seven EVM mainnets and Solana, with import and export of the raw private key both exposed as REST endpoints. Strongest on what a stolen api credential can do before anyone notices (10/10): Raised from 9: the draft's central deduction was a false absence. Read off the create-policy OpenAPI schema (fetched 2026-08-11), `SendEvmTransactionCriteria` — the criteria set for the relayer endpoint itself — accepts five criteria, all enforced server-side: EvmAddressCriterion (destination allowlist/denylist… Weakest on exactly-once execution and stuck-queue recovery (7/10): Raised from 6 on adversarial re-read: the draft asserted CDP publishes no at-most-once semantics, and that is wrong. docs.cdp.coinbase.com/webhooks/wallets (fetched 2026-08-11) publishes a replacement lifecycle: `wallet.transaction.replaced` — "Transaction replaced an existing pending transaction"… Published price: "CDP non-custodial wallets use a pay-as-you-go model with no contracts or minimum commitments." / "Wallet usage is billed in `wallet operations`.

Best forWhat a stolen API credential can do before anyone notices — 10/10
Main tradeoffCDP does publish replacement semantics — a replaced original "will never land onchain" and fires a `failed` event — but it never uses the word nonce, and there is no cancel or nonce-reset endpoint anywhere in the v2 API. After 30 seconds it hands your backend the stuck transaction's gas parameters and expects you to build the replacement yourself. The X-Idempotency-Key that would protect you cannot be reused: the API "Returns an error if the same key is used with different request parameters", so a higher-gas payload needs a NEW key — and if you then omit the optional nonce field, "the API will assign a nonce to the transaction based on the current state of the account." A fresh nonce makes it a second transaction, not a replacement, and both can land. Pin the nonce yourself or the same intent can be mined twice.
Verify before signup"CDP non-custodial wallets use a pay-as-you-go model with no contracts or minimum commitments." / "Wallet usage is billed in `wallet operations`. A wallet operation is consumed by write actions such as wallet creation, message signing, transaction signing, transaction broadcasting, and policy evaluation." / "Read operations are not billed." / table rows: "Send a transaction (sign + broadcast) | 2" and "Policy evaluation (API key auth workflows) | 1" / "Each wallet operation costs **\$0.005**." / "The first **5,000 wallet operations per month** are free." / "Usage is billed at the beginning of each calendar month for the previous month." (docs.cdp.coinbase.com/wallets/pricing, re-fetched as raw markdown and confirmed character-exact 2026-08-11). Recorded for the record only — this page publishes NO cost ranking for relayers, because per-transaction price is already scored on account_abstraction_infra (publishedUnitPrice, 30%) and cost-per-call on rpc_nodes (35%). No criterion below touches this figure. Note the unit is a "wallet operation", not a transaction: a send costs 2, and 3 if an API-key policy is evaluated. Separately, the gas itself is NOT priced here — on the EOA path it is paid from the buyer's own account balance, so no markup or premium is published for it at all.
Methodology

How this category is reviewed

Reviewed on what the relayer is authorised to do, and whether you can keep the address, exactly-once execution and stuck-queue recovery, what a stolen API credential can do before anyone notices, and where the gas float sits and how you get it back.

The order on this page is the published ranking for this category. Every criterion, weight and source behind it is on the methodology page.
Frequently asked

Questions people ask before choosing relayers

What can a stolen API credential actually send?
On OpenZeppelin Relayer the credential that sends your transactions can also delete the limits that bound it. RelayerEvmPolicy carries exactly seven fields and, because additionalProperties is false, the absences are provable: no per-transaction value cap, no function-selector restriction, no daily or monthly ceiling. Only two fields bound a stolen token at all — whitelist_receivers and gas_price_cap — and PATCH /api/v1/relayers/{relayer_id} accepts the policy object, so the same unscoped bearer token can rewrite both, repoint custom_rpc_urls, execute plugins and call POST /sign. It is an operator-error guard, not a security boundary.
If the relayer retries, can the same transaction execute twice?
Not one relayer in this pool can tell you whether a retry charges your user twice. Every provider scored here lands between 4 and 7 out of 10 on exactly-once execution, and the reason is uniform: they publish the words "nonce management, gas estimation and resubmission" and stop. Across all 38 live Gelato relay and Gas Tank pages the strings retry, resubmit, reprice, idempotent, at-most-once, duplicate, cancel, stuck and escalate occur ZERO times, and the two knobs its older docs advertised now survive only on pages Gelato itself files under "Legacy Documentation". Coinbase does state that a replaced transaction "will never land onchain" — and never once uses the word nonce.
Can I get the gas I deposit back out?
Ask before you fund, because one provider's answer is no and it is not written where you would look. Money goes into Gelato's Gas Tank and the only statement in the whole of its documentation about getting it out is "It's important to remember that the current Gas Tank system does not support withdrawals after depositing funds." — published on a VRF integration guide, not on any relay page, and not on the Gas Tank page that the relay setup guide itself links to, which walks through depositing in five numbered steps and never mentions withdrawal. The float is also single-chain and single-token: "Since Gas Tank is deployed on Polygon, you can deposit USDC in one step", funding all 42 mainnets from one bridged balance. Elsewhere the mechanics differ enough to matter — a prefunded balance in a vendor-controlled address, a deposit contract you can withdraw from, a fee taken on-chain out of the transaction itself, or a postpaid invoice — and where a vendor is silent about what happens to a residual balance on shutdown, that silence is recorded here as the finding rather than smoothed over.
Why is there no price ranking on this page?
Because it is already published twice, and printing it a third time would make this site contradict itself. Price per user operation and the markup a vendor adds to the gas it fronts are scored on Account Abstraction Infra; cost per call is scored on RPC & Node Services. Several vendors here sell across those pages on one meter — one bills relay, bundling and node access from a single compute-unit balance whose plan table is already quoted verbatim on the rollup-as-a-service page, and another is already ranked as having the lowest published gas surcharge in its pool, on a different product line from the one ranked here. Publishing a second number for the same company under a new heading would be a contradiction a reader would find before we did. So this page ranks trust and correctness instead: authority over the address, retry semantics, credential blast radius, and float custody. Every provider's published pricing is still recorded verbatim in its entry — it is simply not permitted to move the ranking.
Does the advertised chain list mean the relayer actually works there?
Not reliably. Seven mainnet chains one provider advertises do not resolve at all: Sequence's own OpenAPI servers block publishes relayer hosts for polygon-zkevm, blast, sei, xai, incentiv, laos and rootnet that return NXDOMAIN, and 18 of the 57 published hosts overall have no DNS record (checked 2026-08-11). Nothing on any Sequence page says whether those are deprecated, pre-announced or an oversight, so the published grid cannot be read as a capability list — verify your chain answers before you build on it. A related trap runs the other way: enabling gas sponsorship on Circle requires an ERC-4337 smart contract account, and Circle's own queue table gives that wallet a limit of 1 transaction on Ethereum, Polygon and Avalanche against 32, 16 and 32 for a plain EOA, so the buyer who turns sponsorship on to improve the experience drops to one in-flight transaction at a time on three of the largest chains.
REVIEWEDAugust 11, 2026METHOD4 criteriaCATEGORYrelayers
Not financial advice · For informational purposes only · Always do your own research
ChainChoice
Compare onchain. A brighter future.
© 2026 ChainChoice. All rights reserved.
System statusFeeds last refreshed 9 days ago
Built from commit ba0993b · rankings.json sha256 e1eb24980abb
ChainChoice · The decision layer for crypto · Not financial adviceEducational analysis, not investment advice. Affiliate links may contribute to operations but never alter rankings.

ChainChoice provides informational content only. Nothing on this site constitutes financial, investment, legal, or tax advice. Always do your own research and consult a qualified professional before making financial decisions.