Add proxyd support for routing transactions to ingress RPC

[niran]

Summary

Add support for proxyd from OP Labs to enable transparent routing of RPC methods:

• Transaction submission methods → ingress RPC
• Standard Ethereum RPC methods → op-geth or flashblocks-rpc

Key Features

• Uses production-grade us-docker.pkg.dev/oplabs-tools-artifacts/images/proxyd image
• Method-based routing via TOML configuration
• Automatic selection of backend based on --flashblocks flag
• Custom method routing via CLI flags

Usage

# Basic usage with ingress
builder-playground start opstack --proxyd --ingress-rpc ingress-rpc

# With flashblocks (routes base_meter* methods correctly)
builder-playground start opstack --proxyd --flashblocks --ingress-rpc ingress-rpc

# With custom method routing
builder-playground start opstack --proxyd --proxyd-ingress-methods eth_customSubmit --proxyd-standard-methods debug_customTrace

Implementation Details

Two-Backend Architecture

Ingress backend: Routes transaction submission methods

• eth_sendRawTransaction
• eth_sendBundle
• eth_sendBackrunBundle
• eth_cancelBundle
• eth_sendUserOperation

Standard backend: Routes everything else

• When --flashblocks disabled: op-geth
• When --flashblocks enabled: flashblocks-rpc (handles standard methods + base_meter*)

Default Method Mappings

Includes all standard Ethereum RPC methods (eth_call, eth_blockNumber, etc.) and Base-specific methods (base_transactionStatus, base_meterBundle, etc.)

Custom Method Routing

• --proxyd-ingress-methods: Route additional methods to ingress
• --proxyd-standard-methods: Route additional methods to standard backend

Testing

Tested with:

• Standard RPC methods (eth_chainId, eth_blockNumber)
• Transaction submission (eth_sendRawTransaction)
• Base metering methods (base_meterBundle with --flashblocks)

[ferranbt]

Thank you for the contribution. Could you write the proxyd config in the component itself? This is something I am iterating on to avoid having to go through the artifacts for specific per component configurations. This is an example.

[canercidam]

Hey @niran, thanks a lot for the contribution! With a recently added feature, playground lets you take control of recipes and build your own on top of the base ones by using a playground.yaml like below - without having to add the component in Go like in this PR.

base: opstack
description: Running OP Stack with Proxyd

recipe:
  proxyd:
    services:
      proxyd:
        image: "us-docker.pkg.dev/oplabs-tools-artifacts/images/proxyd"
        tag: "latest"
        args:
          - "/bin/proxyd"
          - "/config/proxyd.toml"
        artifact: "/config/proxyd.toml"
        files:
          /config/proxyd.toml: proxyd.toml
        ports:
          http: 8545

I took the proxyd config template from this PR, picked the endpoint defaults noted down to one of the structs, created a proxyd.toml next to that playground.yaml and started the recipe with builder-playground start playground.yaml - seems to work but I could be doing something slightly off without realizing. 🙂

We also now have test command that lets you quickly send a tx with one of the prefunded accounts (see builder-playground test --help). Maybe that helps you quickly verify your setup.

If you try this, please let me know how it goes - thanks!