A bank can't sign an SLA with Ethereum.
When a blockchain project moves from pilot to production, risk shows up in two places. There’s the risk built into doing business on a public chain, where no one is accountable. And there’s the risk in the infrastructure that connects the bank to that chain, where someone can be.
We power institutions including Kinexys by J.P. Morgan, Visa, Circle and Robinhood, and both come up in our enterprise reviews. Here is what to watch for in each, and what you can do about it.
Four unresolved blockchain challenges, and how banks manage their exposure
Research from the MIT Digital Currency Initiative and Kinexys by J.P. Morgan identifies four challenges that public chains have not solved. Banks can’t remove them, but the right infrastructure controls help manage their exposure.
Risk
Why it matters to a bank
How Alchemy helps
Front-running
Client orders can be exploited
MEV protection on five major chains
Censorship or omission
Settlement timing becomes uncertain
Alerts when a transaction lands or drops
Unsolicited tokens
Unknown assets show up in bank wallets
Real-time alerts on every incoming transfer
Gas fees to sanctioned parties
Possible sanctions exposure
Fee data your compliance tools can screen
Front-running
On most public chains, a transaction doesn't go straight into a block. It first waits in the mempool, a public waiting area that anyone can read. Bots watch the mempool for large trades, then pay a higher fee to get their own trade in first and profit from the price move. The industry calls this MEV, short for maximal extractable value.
The MIT report adds a risk specific to banks. If a compliance team sends a transaction to freeze or seize tokens, the holder can see it coming in the mempool and move the funds first.
The report also finds that 30 to 40 percent of Ethereum transactions already reach blocks through private channels, and that banks may prefer this route because they deal with known, accountable parties. We include MEV protection on our standard endpoints for Ethereum, Solana, Base, Arbitrum and BNB Smart Chain. Transactions sent through Alchemy are routed through private submission channels, so they stay out of public view until they land in a block.
Censorship or omission
Block producers, the validators that assemble each block, choose which transactions to include. They don't have to include yours, and most rank transactions by the fee they pay. How urgent a transaction is doesn't count.
The MIT report gives an example. During a run on a token issuer, holders bid up fees to get their redemptions through. The issuer's own urgent transaction, such as pausing the token, can get priced out of the block.
A payment that might not land when expected is a settlement problem. We can't force a block producer to include a transaction, but we can make sure your team knows right away. Webhooks, automatic messages our servers send to your systems, alert you the moment a transaction is mined or dropped, so your team can resubmit it with a higher fee.
Unsolicited tokens
Anyone can send any token to any address, and one address can receive every token on that chain. Some senders are on sanctions lists. Others spray tokens across thousands of addresses to confuse the analytics tools banks use to trace funds.
A bank has to know what it holds, so every unexpected asset needs to be reviewed and sometimes returned. Our Address Activity webhooks flag every incoming transfer to the addresses you watch, in real time. Spam detection in our NFT APIs helps your team separate junk from assets that need a closer look.
Gas fees to sanctioned parties
Every transaction pays a fee, called gas, to whoever produces the block. On a permissionless chain, there is usually no identity check on who that is, so a small share of a bank's fees could reach a sanctioned party.
Sanctions carry strict liability, so as the MIT report notes, banks treat even a remote chance of exposure as a material risk. Every block records the address that received its fees, and we serve that data so your compliance tools can screen it. We also run OFAC checks on incoming traffic at our edge.
None of these four can be fully fixed by a bank or a provider alone. The lasting fixes sit in the protocol and in regulation, where banks have little direct control. What you can control is how your transactions reach the chain and how fast you see what happens to them.
Infrastructure risk is the part you can contract for
Most banks never touch a public chain directly. Their applications reach it through RPC endpoints, the servers that read chain data and submit transactions. A public chain can't sign an SLA. The company running those endpoints can.
You can't contract with a chain. You can contract with the layer that reaches it.
The industry's own risk framework, written by the Global Blockchain Business Council and Oliver Wyman with DTCC, Euroclear and Kinexys, names RPC endpoints as a third-party risk. It asks banks to vet providers, put SLAs in place, monitor performance, avoid single points of failure and keep a plan for replacing a provider.
Most teams meet that with redundancy at two levels: a primary provider with failover built in, and an independent backup with its own documented failover plan. For transactions, the backup path needs the same care as the primary. Private routing only protects a transaction if every copy stays out of the public mempool, so any backup route should also use vetted private submission, and the failover should be tested before it’s needed.
What this looks like in practice
Say a bank's treasury team settles a payment on Ethereum through Alchemy. Here is the path that payment takes, and where each control applies.
- The bank's application sends the signed transaction to its Alchemy endpoint. The endpoint is tied to the bank's own account, with access set by team and role.
- Alchemy routes the transaction through a private submission channel. It never sits in the public mempool, so no bot can see it and trade ahead.
- The transaction lands in a block, and a webhook tells the bank's operations team. If it had been dropped, a different webhook would fire, and the team would resubmit.
- The compliance team pulls the block data, checks which address received the fee and screens it against sanctions lists in its own tools.
- Days later, an unknown token arrives at the treasury address. An Address Activity webhook flags it, and the team reviews it before anyone touches it.
- Throughout, the Activity Log records who changed the account's settings, and when. If a region goes down, Cortex, the engine behind our platform, moves traffic to a healthy deployment without the bank doing anything.
Each step gives the bank's risk team something it can point to in an audit.
10 questions to ask your infrastructure provider
Bank risk and procurement teams can use these in any supplier review. The right column is how we answer. For a longer list, see our enterprise RPC evaluation guide.
Ask your provider
How Alchemy answers
Will you sign an SLA with uptime commitments and remedies?
Yes. Enterprise plans include signed SLAs
Who do we escalate to, and how fast do they respond?
A named account team, available 24/7
What happens when a region or cloud provider fails?
Multi-region, multi-cloud infrastructure with autonomous failover, powered by Cortex
What uptime have you delivered under extreme market stress?
99.99% through the largest liquidation event in crypto history, October 2025
How do you protect our transactions from front-running?
MEV protection included on five major chains, with no setup
Can you share a current SOC 2 Type II report?
Yes, through our Trust Center
Do you support single sign-on and IP allowlisting?
Yes. Single sign-on through your identity provider (SAML) and IP allowlisting on enterprise accounts
Can we separate access by team and role under one contract?
Yes, with organizations and roles
Is there a record of who changed what in our account?
Yes, the Activity Log
Can we run on single-tenant infrastructure, and how simple is our fallback plan?
Dedicated Clusters for isolation. We use JSON-RPC, the standard interface across providers, on 100+ chains, so any fallback stays simple
Our post on Alchemy's enterprise-grade security covers how our security team works in more detail.
Send us your vendor questionnaire
If your team is working through blockchain risk, send us your questionnaire. We'll come back with the SOC 2 report, SLA terms and engineers who can answer your risk team's questions.
FAQ
Why can't banks treat a public blockchain like a vendor?
A public blockchain has no single owner who can sign a contract or take responsibility for an outage. Banks manage technology risk through direct control or vendor contracts, so they hold their infrastructure provider to the accountability the chain can't offer.
What are the biggest blockchain risks for banks?
Research from the MIT Digital Currency Initiative and Kinexys by J.P. Morgan names four: front-running, transaction censorship or omission, unsolicited tokens, and gas fees paid to sanctioned parties. Each one touches an existing bank obligation, from protecting client orders to sanctions compliance.
What is MEV, and why does it matter to banks?
MEV, or maximal extractable value, is the profit others can take by reordering, inserting or delaying transactions they see in the public mempool. For a bank, it means a client order could be front-run before it settles.
How should a bank plan for an RPC provider outage?
Use an accountable primary provider with redundancy built in, plus an independent backup with a documented, tested failover plan. Alchemy runs across multiple regions and cloud providers with autonomous failover, and standard JSON-RPC keeps a fallback plan simple.
Does Alchemy protect bank transactions from front-running?
Yes. Alchemy includes MEV protection on standard endpoints for Ethereum, Solana, Base, Arbitrum and BNB Smart Chain. Transactions are routed privately until they are included in a block. Protection covers transactions sent through Alchemy. If you also send copies through a backup provider, that route should use private submission too, so no copy reaches the public mempool.
Can technology alone solve sanctions exposure on public blockchains?
No. The MIT Digital Currency Initiative's research with Kinexys by J.P. Morgan says risks tied to front-running, sanctions exposure and unsolicited tokens cannot be fully addressed through technical means alone. Banks need protocol changes, clear regulatory guidance and strong internal controls working together.












