Keep wallet context attached to every task
Organize wallets you control and choose the network and asset for each operation. Review balances and permissions without treating every address as interchangeable.
Multiple Wallets. One Operational Workspace.
Coordinate multi-wallet operations, batch token transfers and asset consolidation with clear sources, destinations, fee reserves and local signing.
Many wallets. One legible operation map.
Trace each source to its destination without losing the reserve or task context.
01 / 05
Select the source wallets
The illustrated A, B and C wallets are labels, not real addresses or funded accounts.
Plan generation is not a signature. Provider acceptance is not confirmation. Review the actual result before retrying.
FRB / WINDOWS
The wallet workspace, in the application.
An existing application capture alongside the illustrated operation map. Enlarge it to inspect the wallet workspace; the diagram above explains the proposed flow.
Workspace screenshot with sensitive values redacted. Displayed values are not evidence of returns or a live connection.
Prepare transfers with visible destinations
Check source and recipient lists, amounts and token compatibility. Reserve native assets for fees and review each proposed transfer before local signing.
Consolidate without losing the outcome trail
Sweeper workflows bring selected assets to a destination you review. Reconcile individual results and partial failures before creating another transfer attempt.
Build an agent around your rules.
Define the task
Give the agent a specific goal and the wallet and network context it needs. Resolve missing inputs before moving on.
Set the boundaries
Keep amounts, destinations, permissions and execution limits explicit. Review the proposed actions instead of granting an open-ended mandate.
Review the handoff
Inspect preparation and simulation separately from approval, local signing and submission. Check each returned outcome.
EVM and Solana. The right execution context.
EVM workflows
Review chain ID, wallet permissions, nonce, gas and the configured RPC or private-submission provider. Flashbots routes depend on chain and provider support.
Solana workflows
Review accounts, token programs, blockhash validity, fees and the selected RPC or Jito route. Bundle acceptance, inclusion and confirmation are different states.
Control stays visible.
Local transaction signing and AI inference are different boundaries. Review the AI provider and what context it receives. Keep private keys, seed phrases and provider credentials out of chat. Protect your Windows device and verify every operation before approval.
Control stays visible.Before you build your workflow
Is FRB a custodial exchange or a wallet?
FRB is a non-custodial execution workspace for your wallets. It organizes network context, operations and approvals while transaction signing stays on your Windows device. You control the wallets and provider connections; FRB is not a hosted account holding your balance.
How is FRB different from a chatbot?
FRB connects AI chat to structured trading workflows: wallet and network context, a reviewable operation plan, approval and local execution. A chat response alone is not an executed trade.
Does an agent mean unlimited automatic trading?
No. Define the task and its boundaries, review the proposed actions and retain approval over signing. Do not treat an agent as an unrestricted mandate.
Does all AI run locally?
Local signing does not imply local AI inference. Review your chosen AI provider and the context sent to it. Never put private keys or seed phrases into a prompt.
Does AI guarantee profit or bundle inclusion?
No. Market prices, liquidity, fees, ordering and provider conditions still affect the outcome. Simulation, AI output and submission acceptance do not guarantee execution or returns.
Can I run the agent on my phone?
FRB Agent runs on Windows. You can read these guides on mobile and copy the download link for your Windows computer. Use the matching EVM or Solana dashboard to connect the installed agent.