← Opportunities

OP Security Proxy: Local Pre-Execution & Revert Interception for the Superchain

Trust breakdown (3/3 checkable facts verified)

Fit breakdown (against the ORG_* profile)

Sources (1)

History (1)

Extracted text

Hi everyone. I am a solo systems developer building OP Security Proxy ([GitHub - Ishant5436/op-sec-proxy · GitHub](https://github.com/Ishant5436/op-sec-proxy)), which is an open-source JSON-RPC middleware written in Rust that intercepts and simulates transactions before broadcasting to OP Stack nodes. On EVM rollups, end users and automated agents pay gas fees even when transactions revert on chain due to stale oracle states, localized slippage, or sandwich attacks. For retail users, burning gas on a failed execution creates frustration, and for wallet teams it leads to avoidable support tickets.

The proxy sits between standard wallets or clients and public Optimism RPC nodes. When a client issues an eth\_sendRawTransaction request, the proxy intercepts the raw payload and simulates it in process using revm against current chain state. If the simulation executes successfully, the transaction is forwarded upstream to the sequencer over an existing hyper connection pool. If the simulation reverts, the proxy aborts the broadcast completely so zero gas is burned on chain, and immediately returns a standard JSON-RPC error containing decoded Solidity custom errors or panic codes along with an estimated gas saved metric.

The core implementation is open-source under the MIT license with 40 automated tests passing across the Rust core and TypeScript client SDK. In empirical benchmarks against [mainnet.optimism.io](http://mainnet.optimism.io), the proxy introduces a minimal 11.8 millisecond processing overhead on fair keep-alive connections with session reuse. For clients that make cold requests without connection reuse, the proxy internal connection pool eliminates repetitive TLS 1.3 handshakes to remote endpoints, amortizing roundtrip latency by roughly 97 milliseconds. The full reproduction methodology and raw telemetry logs are recorded in BENCHMARK\_RESULTS.md ([https://github.com/Ishant5436/op-sec-proxy/blob/main/BENCHMARK\_RESULTS.md](https://github.com/Ishant5436/op-sec-proxy/blob/main/BENCHMARK_RESULTS.md)).

Uncached transaction simulation over public internet RPC currently averages approximately 2.7 seconds because the execution engine must fetch contract state slots across the network during execution. I am requesting 10,000 OP for an initial builder grant to fund three engineering milestones over the next three months. The initial phase tackles state caching, replacing network RPC state queries with a local in-memory LRU trie cache for warm contract bytecode and storage slots to drive simulation latency down toward a sub-65 millisecond target. Following that, work shifts to developer adoption with a TypeScript provider wrapper and standardized error decoding for wallet integrations. The final phase expands routing across OP Mainnet, Base, Mode, Zora, and Fraxtal alongside reproducible Docker containers and systemd service packaging for node operators.

As an individual engineer, I rely on Rust memory safety guarantees, cargo-audit automated dependency scanning, and reproducible GitHub Actions workflows rather than corporate support infrastructure. All code is public and modular. I previously shared an introductory post in the general discussion section of the governance forum under thread 10810 ([OP Security Proxy: A local RPC middleware to prevent paying for failed L2 executions](https://gov.optimism.io/t/10810)), and this grant application will allow me to build and package the middleware as a permanent, zero-cost public good for the Superchain ecosystem.