EIP-7966 Explained: A New RPC Method to 2x App Throughput – Example from Ethereal Inside
Fast chains need fast RPCs. That’s why we co-authored EIP-7966: A proposal for a new RPC call that both submits a signed transaction and gets the receipt as soon as the transfer is included, rather than executing two requests separately. This small but high-impact change cuts the transaction submission-to-confirmation time in half, essentially doubling throughput for high-speed onchain apps across trading, gaming, payments, and more.
The RISE team created this EIP, and we’ve already implemented it on Arbitrum testnet for some of our customers. Below, we’ll tell you everything you need to know about EIP-7966 and provide a brief case study showing the improvements it’s made on testnet for one high-throughput DEX: Ethereal.
What is EIP-7966? Explaining the eth_sendRawTransactionSync method
EIP-7966 introduces a new RPC method for onchain apps: eth_sendRawTransactionSync. We’ll explain how it works, but first, let’s look at how most apps submit transactions via RPCs today.
Currently, apps execute transactions using a two-step flow:
- App sends transaction using eth_sendRawTransaction. The node immediately returns the transaction hash.
- App repeatedly polls the node using eth_getTransactionReceipt(txHash) until the node returns the receipt confirming the transaction made it into a block.
Each poll is a separate RPC roundtrip that must take place until the app gets the receipt and confirms the transaction’s inclusion.
eth_sendRawTransactionSync reduces that flow to a single RPC call, in which the app both submits the transaction and waits until a custom timeout that they decide for the node to return the receipt. The recommended custom timeout is 2 seconds maximum, but in practice, most calls get their receipt in milliseconds. If the timeout period passes, the app reverts back to the standard polling method so that nothing is disrupted.
Benefits of EIP-7966
EIP-7966’s primary benefits are increased speed and throughput. By collapsing the send + poll workflow into a single request, eth_sendRawTransactionSync can cut the time from transaction submission to receipt by 50%.
This means that apps using the new method can process twice as many transactions in a given time period, improving UX and potentially doubling fee revenue, without adding new RPCs. From an ecosystem perspective, this new method reduces the load on RPC nodes by eliminating the continuous loop of polling that follows most app transactions. EIP-7966 is especially useful for appchain operators, who need to worry about the app’s UX and economics as well as the chain’s overall infra load, as eth_sendRawTransactionSync improves both.
EIP-7966 has clear benefits for a number of onchain use cases:
- Trading. DEXs, CLOBs, and other trading apps can double their fee revenue by processing twice as many transactions per second, with no modification to block times or gas limits. The increased speed also allows these apps to offer tighter spreads, reduce stale quotes, and increase order execution probability – all of these improve UX.
- Gaming. Many onchain games translate rapid, repeated in-game actions (e.g. moves, item trades, crafting, etc.) into individual transactions, each of which generates a polling loop under today’s eth_sendRawTransaction paradigm. EIP-7966’s introduction of synchronous receipts reduces the load on RPCs by eliminating those loops and provides smoother gameplay for users.
- Payments. Onchain payments apps with high volumes can process more payments – and therefore generate more fees – with EIP-7966’s eth_sendRawTransactionSync method. This method also allows them to confirm payments faster and eliminate the anxiety users get waiting for a big transfer to be confirmed – a huge UX win.
Below, we’ll look at how EIP-7966 has drastically improved latency and throughput on testnet for Ethereal, a DEX chain launching soon on mainnet.
EIP-7966 case study: 10x latency improvement on Ethereal testnet
Ethereal is a high-performance trading app launched in October 2025 as an L3 on Arbitrum, powered by Conduit. We implemented EIP-7966 on Ethereal’s testnet in mid-September 2025, at the same time that we relocated its RPC cluster to the APAC region closer to the chain’s core infrastructure. Together, these changes made for a 10x latency improvement, with total transaction times dropping from a 500-800ms range to a consistent 50ms.
Increased speed means Ethereal can process more orders, leading to a direct increase in fees. It also meaningfully improves the product for traders and market makers – a 10x latency improvement is in effect a 10x reduction of the risk window for each order Ethereal processes. That means tighter spreads and fewer stale quotes. If that improved UX increases orders by even 10%, it could mean millions more in yearly revenue for the app.
EIP-7966 is an RPC unlock benefiting all onchain participants
EIP-7966 is one new RPC method with an outsized impact on onchain economics and UX. By replacing the transaction submission + receipt polling loop workflow with a single call for transaction submission and receipt return, EIP-7966 reduces latency and infra load while improving throughput – all crucial benefits as chains get faster and look to onboard users from web2. We’ve already rolled this method out manually to some Conduit chains, and look forward to expanding this capability to the entire Ethereum ecosystem if the EIP is approved.