What local execution does—and does not—mean

Local execution describes where an application runs and where signing is handled. It does not mean every data request or transaction route stays on your computer: RPC providers, network paths, relays, and builders may remain external.

FRB Agent is a non-custodial Windows application, and signing keys remain local. This product boundary does not by itself prove that a selected endpoint is local or that a transaction is private.

Three separate questions to evaluate

Key control

Check where keys are created and stored, what actions the application can authorize, and which steps require your approval. Keep the release and device security in scope.

Network path

Identify each RPC, WebSocket, relay, and builder involved. Record which provider receives data and what happens if it rejects, delays, or cannot process a request.

Simulation

Confirm which chain, block state, inputs, and provider responses are used. A simulation is a conditional review of that setup, not a promise about a later block.

A practical due-diligence checklist

Ask for observable product behavior and provider documentation rather than relying on labels such as “local”, “private”, or “protected”.

Signing boundary

Can you verify where signing occurs and whether private keys leave your device? Review permissions and the official security documentation.

Simulation scope

Which state and block context are simulated? Which contracts, network conditions, or changing inputs are outside the simulation?

Submission and inclusion

Which endpoint receives the signed transaction or bundle? What are its inclusion conditions, failure behavior, and fallback routes?

Costs and recovery

Account for network fees, slippage, failed transactions, liquidity changes, and market losses. Decide how you will monitor and recover from endpoint or device failures.

Important limits

A locally run application still depends on the machine, its configuration, and external network services. Simulation results can differ from later chain state; private submission does not guarantee inclusion, ordering, or protection from every form of MEV. Check the selected provider’s current documentation.

Primary technical references

FRB Agent product boundary

FRB Agent is a non-custodial Windows execution assistant with local signing keys. Review the setup, security, pricing, and risk information for the current release; do not infer additional infrastructure features from this general guide.

Read the quickstart
Control the Pulse

Expand Your Execution

Maximize your edge by exploring the full FRB toolkit. From institutional-grade telemetry to ready-to-export strategy scripts.

Ready to Evolve?

Take the Next Step

Whether you're verifying terminal security or launching your first bundle, the FRB journey starts here.

Recommended

Install FRB Agent

Secure Windows build. Verified via SHA-256 for maximum integrity.

Recommended

Read Docs Quick Start

Master the setup in 15 minutes. From wallet pairing to first bundle.

Recommended

Launch Dashboard

Monitor your Ops Pulse and manage transaction routes in real-time.