Security and risk

BRO-ker is a high-risk trading tool that can sign transactions from managed in-bot wallets. Security depends on the official Telegram account, your Telegram session, BRO-ker's systems, third-party providers, the selected blockchain, token contracts, and your own decisions.

Use a dedicated wallet, limit its balance, and retain an offline backup.

Wallet model

Wallet signing material is encrypted in server-side storage and used to sign manual actions you confirm and automation you configure. This is not strict self-custody because the signing environment is not solely under your local control.

For long-term storage or funds you cannot afford to lose, use a wallet architecture appropriate to that purpose rather than an active trading bot.

Protect your account and keys

• Use only the official bot found through verified BRO-ker destinations.
• Enable Telegram two-step verification and protect active Telegram sessions.
• Never send a private key, recovery phrase, login code, or backup screenshot to support.
• Store wallet backups offline and test that they restore the expected address.
• Keep separate wallets and limited balances for automation.
• Review active copy rules, limit orders, approvals, and connected funding sessions regularly.

Anyone with your Telegram account can potentially initiate actions visible to that account. Anyone with a wallet key or recovery phrase can bypass BRO-ker entirely and control the on-chain assets.

Verify every asset and network

Token names, symbols, images, websites, and social profiles are not unique. Use the complete mint or contract and verify it against an independent trusted source.

Ethereum, Base, Robinhood Chain, and Arc are different networks even when an address format looks similar. Arc is currently testnet-only; do not send mainnet assets to an Arc destination.

Quotes and execution

A quote is a time-limited route estimate, not a guaranteed price. Review input, output, minimum received, slippage, price impact, route, fees, expiry, wallet, network, and token identity.

Execution can fail or differ because of market movement, liquidity, transfer fees, taxes, gas, congestion, block expiry, provider changes, smart-contract behaviour, or blockchain reorganisation.

ERC-20 approvals are independent on-chain permissions. Confirm the token, spender, amount, and network. Remove approvals you no longer need through a reputable network-specific service.

Automation risk

Limit orders and copy trading can transact without a new manual confirmation for each fill. Funds are not reserved for local limit orders, and source-wallet actions can be detected after the market has already moved.

Use maximum sizes, daily caps, reserves, risk filters, stop conditions, and notifications. These controls reduce exposure but can fail because of missing data or rapidly changing on-chain conditions.

Provider and bridge risk

BRO-ker depends on RPC services, market-data sources, route providers, block explorers, Coinbase Hosted Onramp, bridge infrastructure, and supported protocol contracts. A provider can be delayed, unavailable, compromised, or return incomplete data.

Bridge transactions add cross-chain contract, relayer, liquidity, settlement, and destination-network risk. Do not repeat a bridge whose status is uncertain until the source transaction and route state have been checked.

Coinbase handles its own identity, payment, eligibility, fee, and settlement process. BRO-ker will not ask for Coinbase credentials or payment details in Telegram.

Analytics and warnings

Token scans, warnings, market data, PnL, charts, leaderboards, and portfolio values are informational. They can be stale, incomplete, spoofed at the source, or based only on activity BRO-ker tracked. They are not audits, tax records, financial advice, or guarantees.

If you suspect compromise

1. Stop using the affected bot session and secure your Telegram account from a trusted device.
2. Pause copy-trading rules and cancel still-open bot-managed orders if you can do so safely.
3. From a trusted wallet, move remaining assets to a new wallet whose key has never been exposed.
4. Review recent transactions, token approvals, active Telegram sessions, and funding activity.
5. Contact support only through an official destination shown by /bro_socials.

On-chain transactions already confirmed cannot be reversed by BRO-ker.