Local signing. Private execution paths. Control over your capital.
Download for Windows · Quick Start · Documentation · FRB Labs on GitHub
Your trading strategy should not require handing a server the keys to your capital. FRB Agent brings non-custodial EVM and Solana execution to Windows, combining local signing, simulation-first review, and private bundle workflows for traders and MEV searchers who want control over each operation.
Start with a verified download and a simulation. Software access has no required subscription; a 20% performance fee applies to qualifying net profitable executions where the fee logic applies. Network fees, validator tips, slippage, and trading losses remain separate considerations. Review pricing.
Why local custody · Execution engines · Architecture · Install and verify · Research · Official links
When a hosted trading service stores a usable private key, its infrastructure becomes part of your wallet's security boundary. A server compromise, malicious insider, or privileged database administrator with access to both encrypted keys and decryption material can turn an application incident into a signing incident. Encrypting keys on the same service that can decrypt and use them does not remove that dependency.
FRB's published model keeps signing on your Windows device. The operator selects the wallet, transaction permissions, provider, and execution limits; the local agent prepares and signs the operation. Signed transaction data can leave the device for submission, while private signing keys remain local. Local execution architecture.
| Dimension | FRB Agent | Telegram trading bots using hosted keys | Wallets submitting through public RPC |
|---|---|---|---|
| Key custody | Local signing; Windows DPAPI storage is described in FRB's security documentation. | Provider infrastructure holds or can use signing authority. | Usually local or hardware-wallet signing; check the wallet. |
| MEV protection | Supported Flashbots, Titan, and Jito paths reduce public pre-inclusion exposure. | Depends on the bot's provider, route, and fallback policy. | Ordinary public broadcast can expose transaction intent; private endpoints change that model. |
| Execution latency | Device-to-provider path; affected by connection quality, region, provider, and chain conditions. | Hosted infrastructure may be well located; interface and service hops also matter. | Depends on endpoint, connection, wallet behavior, and network load. |
| Simulation | Supported preflight and simulation before approving execution. | Product-specific; inspect what is simulated and against which state. | Often transaction-level checks; bundle support varies. |
| Multi-chain | EVM and Solana workflows; available operations and routes vary by release and provider. | Product-specific network and strategy coverage. | Depends on the wallet and configured networks. |
| Local control | Local execution environment, wallet configuration, permissions, and route review. | Signing service, updates, and availability are controlled by its operator. | Local approval, with submission delegated to the selected RPC. |
Note
These columns compare custody and execution models, not every product using a Telegram or browser interface. A web app can use local signing, and a hosted service can use restricted delegated permissions. Evaluate the actual signing authority, permissions, and network path. The table is not a latency benchmark. Comparison methodology.
Use FRB's Solana workflow to prepare operations for the configured Solana RPC or supported Jito Block Engine route. Review the ordered transactions, account requirements, blockhash validity, and expiry before submission.
- Jito bundle tipping: set a tip policy and total fee budget using current route requirements; a tip is a competitive bid, not a guarantee of inclusion.
- Private block-engine routing: use the supported Jito path to reach its validator execution pipeline without assuming an ordinary RPC submission has the same privacy properties.
- Anti-sandwich controls: combine private routing with explicit slippage, size, and expiry limits. Inspect fallback behavior before enabling a live route.
- Outcome tracking: distinguish a returned bundle identifier from inclusion and confirmation; check the resulting transactions on-chain.
Solana setup guide · Open the Solana dashboard.
FRB documents private submission through Flashbots and builder routes including Titan. Select a route supported by the installed release and target chain; Ethereum builder support does not imply equivalent support across every EVM network. Private bundle workflows.
- Ordered bundles: prepare related transactions and review target-block, nonce, expiry, and allowed-revert conditions.
- Gas and priority controls: review base-fee assumptions, priority bids, builder payments, and spending caps as network conditions change.
- Preflight review: inspect the exact transaction sequence against the selected state before approving local signing.
- Submission reconciliation: retain the provider result and verify the final receipt before retrying an unresolved operation.
Important
Private routing reduces public-mempool exposure; it does not make a transaction invisible to its relay or builder, or provide complete immunity to sandwich attacks and other MEV. Privacy, ordering, atomicity, fallback, and inclusion depend on the route. Jito's documented rebroadcast cases also limit bundle atomicity. Transaction ordering and execution limits.
FRB's published security model describes Windows DPAPI encryption at rest, key loading into the local process for signing, and submission of signed transaction bytes without transferring private keys to FRB's backend. The release notes separately document DPAPI protection for pairing credentials. Security model · Release metadata.
This separates local key custody from the hosted coordination service. It does not turn Windows into a hardware wallet: malware running with sufficient local privileges, unsafe approvals, and malicious updates remain relevant threats. The public documentation does not establish a per-signature key-erasure guarantee. This separates local key custody from the hosted coordination service. Windows DPAPI protects stored secrets; device security and transaction permissions remain essential to protecting the signing process.
Use a dedicated execution wallet, protect the Windows account, and review destinations and spending permissions. Keep seed phrases, private keys, and provider secrets out of dashboards, AI prompts, logs, and support messages. Consult the telemetry policy for diagnostics and controls.
Start with supported simulation and preflight workflows to inspect an operation without sending a live trade. Record the chain state, transaction inputs, fee assumptions, and provider so the result can be reviewed and reproduced. Simulation mode.
Review expected asset changes, gas impact, slippage limits, reverts, and any available profit estimates. A useful review model is:
Estimated net PnL = estimated proceeds after price impact and slippage
- input asset cost
- network fees
- validator tips or builder payments
- applicable FRB performance fee
Use one valuation currency and avoid counting costs twice. This is an evaluation framework, not a claim that every workflow exposes a complete PnL calculator. A successful simulation cannot predict subsequent liquidity, ordering, or market changes. Reproducible simulation template.
The diagram summarizes the published local-signing model and separates coordination from transaction submission. It is a conceptual trust-boundary map, not an audited description of every request.
flowchart LR
subgraph DEVICE[User-controlled Windows device]
WALLET["Wallet and local key storage"]
AGENT["FRB Agent<br/>Review, simulate, sign"]
WALLET <-->|Local signing| AGENT
end
DASH["EVM or Solana dashboard"]
HUB["FRB coordination hub"]
RPC["Configured RPC providers"]
subgraph ROUTES[External private execution providers]
EVM["Flashbots / Titan<br/>Supported EVM builder routes"]
JITO["Jito Block Engine<br/>Supported Solana bundle route"]
end
EVMCHAIN["EVM block production and nodes"]
SOLCHAIN["Solana validators and nodes"]
DASH <-->|Pairing and workflow status| HUB
HUB <-->|Secure coordination connection| AGENT
AGENT <-->|Chain state, preflight, receipts| RPC
AGENT -->|Signed transactions or bundles| EVM
AGENT -->|Signed transactions or bundles| JITO
EVM -->|Conditional inclusion| EVMCHAIN
JITO -->|Conditional inclusion| SOLCHAIN
EVMCHAIN -->|On-chain results| RPC
SOLCHAIN -->|On-chain results| RPC
Local execution still depends on network services. The dashboard pairs with the agent; the selected provider receives submission data; blockchain results establish whether execution occurred. The diagram shows private submission paths; ordinary RPC submission has different visibility properties. Architecture guide · Pairing instructions.
Requirements: Windows 10 or 11, 64-bit; .NET Framework 4.8; and network access to the selected dashboard, RPC, and relay services. Installation guide.
- Download from the official site. Open FRB downloads, choose the appropriate network workflow, and save the Windows installer.
- Verify the file before opening it. Compare its filename and SHA-256 with the official release metadata using the command below. Stop if verification fails.
- Install and open FRB Agent. Follow the setup wizard, review the license, and keep Windows endpoint protection enabled.
- Pair the matching dashboard. Open EVM or Solana and enter the six-character pairing code displayed by the agent. Confirm its actual connection status.
- Configure and simulate. Review the wallet, network, provider, destinations, permissions, fee budget, and slippage limits. Resolve preflight failures before approving live execution.
- Verify the outcome. Check provider acceptance, inclusion, and confirmation separately. Inspect unresolved submissions before retrying.
The following fingerprint was checked against the official release metadata and the downloaded installer on 28 October 2026. The installer was downloaded for integrity verification and was not executed.
| Release | Published date | Windows installer | Exact size |
|---|---|---|---|
| v8.6 | 15 August 2026 | FrbAgent_install_vr_8.6.exe |
14,536,045 bytes |
| Algorithm | Expected digest |
|---|---|
| SHA-256 | 3fcec860272e137df8237c7af3b07d78ba66a5d1a5589d03b844cac00946956c |
Sources: Release history · Current release API · Release manifest.
PowerShell one-liner — checks this exact release in your Downloads location and stops on a mismatch:
$expected = '3fcec860272e137df8237c7af3b07d78ba66a5d1a5589d03b844cac00946956c'; $file = Join-Path $env:USERPROFILE 'Downloads\FrbAgent_install_vr_8.6.exe'; if ((Get-FileHash -LiteralPath $file -Algorithm SHA256 -ErrorAction Stop).Hash -ne $expected) { throw 'SHA-256 mismatch. Do not run this file.' }; 'SHA-256 matches the documented v8.6 release.'Tip
The version badge follows the current release API; the table records the specific artifact checked above. If the published file changes, obtain its matching checksum from the official release page. A matching hash confirms agreement with published bytes, not an independent security audit.
| Endpoint | Useful fields |
|---|---|
/api/version |
version, date, file.name, file.sha256, file.bytes, file.downloadUrl |
/releases.json |
latest, releases[], release notes, and per-file metadata |
These public endpoints support release tracking and integrity checks. Neither an update response nor a download should automatically authorize execution.
FRB publishes incident analysis, architecture guidance, and reproducible evaluation materials. Use their evidence and limitations when assessing key custody, MEV protection, or provider performance.
| Publication | What it helps you evaluate |
|---|---|
| COLDCARD RNG incident: technical root cause and on-chain observations | Entropy failures, firmware control flow, and bounded blockchain evidence. Includes primary-source references and separates observed fund flows from attribution. |
| WSS/RPC measurement methodology | Repeatable endpoint measurements with environment, sample size, failures, percentiles, and inclusion kept separate. |
| Dated RPC/WSS observations — 29 August 2026 | A small public-endpoint dataset with reproducibility limits; it is not a private-RPC ranking or an FRB trading-performance benchmark. |
| Execution provider comparison methodology | How to compare local clients, hosted services, private RPCs, and block engines using consistent evidence. |
| Non-custodial vs. hosted-key trading models | FRB's analysis of key custody, local signing, and delegated trading authority. Assess each provider's current implementation separately. |
| Execution security and permissions checklist | Release review, key lifecycle, spending permissions, network dependencies, and incident readiness. |
| Simulation test template | A structured record of inputs, assumptions, failure cases, and the decision to approve live execution. |
These are published technical resources, not evidence of an independent audit of FRB. The COLDCARD research does not establish that FRB prevents hardware-wallet entropy failures.
| Destination | Official link |
|---|---|
| Website | ai-frb.com |
| Windows download | Download FRB Agent |
| Release history and checksums | Releases |
| Documentation and onboarding | Documentation · Quick Start |
| Trading workspaces | EVM dashboard · Solana dashboard |
| Security and disclosure | Security policy · Report a vulnerability |
| Costs and policies | Pricing · Terms · Risk disclosure |
| Privacy and diagnostics | Privacy · Telemetry |
| Developer presence | GitHub @FRBLabs |
| Community and launch | X @FRBLabs · Product Hunt |
| Help | Support |
For sensitive security findings, use the official disclosure channel; never attach signing keys or seed phrases to a public issue.
FRB software is supplied under the published license terms, which describe a limited, revocable, non-transferable license and an as-is basis. Free download access does not grant an open-source license to the application.
FRB provides execution software, not investment advice, asset management, or guaranteed returns. Non-custodial architecture describes where signing authority resides; it does not remove transaction risk or establish regulatory approval. Users remain responsible for authorized use, wallet permissions, configuration, and applicable laws.
MEV strategies and digital-asset trading can result in loss of capital. Simulation, private routing, and positive estimates do not guarantee profitability, inclusion, ordering, or execution success. Review the risk disclosure, pricing, and terms before live use.
Build your execution workflow around keys you control.
Download FRB Agent ·
Verify, pair, and simulate ·
Explore FRB on Product Hunt
Documentation and release information reviewed on 28 October 2026. Product capabilities are described from official public materials; this README does not constitute a source-code audit.