Abstract

The FRB Agent employs a Local Execution Architecture, shifting the computational load and cryptographic authority from a centralized server to the user's local hardware. This architectural choice defines it as "Infrastructure" rather than a "Service," ensuring that the operator (the user) retains absolute sovereignty over strategy execution and private keys.

The Consensus-Client Binding

Unlike cloud-based bots that rely on remote API calls to trigger transactions, FRB Agent runs as a sidecar to the user's local or commercial blockchain node.

UserPC[User Hardware] -- "1. Strategy Logic" --> Agent[FRB Execution Client]
Agent -- "2. Mempool Scan (IPC/WS)" --> Node[Geth/Reth Node]
Agent -- "3. Bundle Construction" --> Builder[Flashbots Builder]
Builder -- "4. Inclusion" --> Chain[Ethereum Mainnet]

1. Zero-Hop Latency: By running on the same machine or local network as the node, the agent eliminates network jitter between the strategy engine and the state source.
2. Privacy Preservation: Strategy parameters and target opportunities are processed in volatile memory locally. They are never serialized to a centralized database.

Client-Side Strategy Engine

The core differentiation of FRB Agent is its Client-Side Strategy Engine.

• Hosted Bots: You send funds to a contract; the bot decides what to buy/sell. (Custodial Risk)
• FRB Agent: You define logic locally; the agent uses your keys to sign user-authorized intents. (Non-Custodial)

Execution Flow

1. Signal Detection: The agent monitors pending transactions via WebSocket subscription.
2. Simulation: It simulates the impact of a potential bundle against the current block state locally.
3. Construction: If the simulation is profitable, it constructs a bundle.
4. Signing: The agent requests a signature (or uses a strictly scoped local key) to authorize the transaction.
5. Propagation: The signed bundle is sent directly to the block builder relation, bypassing the public P2P mempool.

Infrastructure vs. Service

FRB Agent provides the roads (connections to relays, decoding logic, simulation engine), not the car (the strategy itself). This distinction is critical for regulatory and semantic clarity. It is a tool for interacting with the blockchain's market mechanisms, identical in nature to a specialized wallet or an advanced RPC client.