How to evaluate a Telegram-distributed trading bot

Questions to verify before connecting funds

1. Who controls the signing keys? Confirm whether keys remain on your device, are encrypted locally, or are uploaded to a service. Never share a seed phrase with an operator or support account.
2. What permissions does the software request? Review token approvals, withdrawal permissions, API credentials, and any contract interaction. Use the narrowest permissions available.
3. Where does each transaction go before inclusion? Check the documented RPC, relay, or bundle route and what the provider says about visibility, forwarding, failed transactions, and fees.
4. Can you verify the software and its updates? Prefer official release pages, signed or hashed artifacts where provided, version history, and a clear way to receive security notices.
5. What are the complete costs and support terms? Read fee conditions, refund terms if any, support scope, and incident contact details. Do not infer an SLA or refund promise from marketing copy.

FRB Agent: documented product scope

• FRB is a non-custodial Windows execution assistant; signing keys are kept locally.
• The workflow is simulation-first and includes private-bundle workflows on supported routes. Route availability and behavior depend on the selected provider and chain.
• The software is free to download and use. Where the fee mechanism applies, the fee is 20% of qualifying net profitable executions; review the current pricing page for conditions.

Verify these details in the official security, releases, and pricing documentation.