Assess a crypto trading bot in three separate ways: access security concerns who can use your account and credentials; execution reliability concerns what happens to orders when a component fails; trading risk concerns what the strategy can lose. A well protected service can still run a losing strategy, and a profitable backtest does not establish secure key storage.
This article is published by TradeMatic's developer. It offers criteria to apply to TradeMatic and other products; it is not an independent product audit, security certification or assurance against loss. The aim is to collect enough evidence to make an informed connection decision. No bot is completely safe or free of trading risk.
1. Establish who controls the money and trading access
Start with the path your money takes. “Non-custodial,” “cloud” and “self-hosted” describe different arrangements, but a label alone does not establish who can act on the account.
| Model | What to establish |
|---|---|
| A cloud bot connects to an exchange through an API | Trading capital stays at the exchange. The service receives the powers granted to its API key. Exchange custody, account restrictions and misuse of trading permissions remain relevant. |
| You run the bot on your own device or server | You take responsibility for the device, updates, credentials, backups and remote access. Check whether any third party still receives secrets or can update the running software. |
| The service accepts trading capital into its own accounts or wallets | You also depend on the custodian and its withdrawal or repayment terms. Establish the recipient, control of the funds and the process for getting them back. |
A software subscription and a transfer of trading capital are different transactions. Paying for access to a bot is not by itself evidence of fraud. The payment's purpose, recipient, service period, renewal and cancellation terms should be clear. If asked to “top up,” establish whether this means funding your own exchange account, paying a software fee or handing capital to someone else.
2. Grant only the API permissions the bot needs
An API key lets software perform permitted actions on an exchange account. Reading balances may require only read access; placing orders requires the corresponding trading permissions. Withdrawal access, transfers, derivatives and other operations must be assessed separately. Ordinary Spot automation does not justify extra permissions without an explained need.
Create a separate key for the particular service where possible. Compare the developer's requirements with the permissions actually saved in the exchange account. Know where to review them and revoke the key yourself. For Bybit examples, use Bybit Global documentation and your own account interface; do not carry over Bybit EU or another regional platform's settings automatically. The Bybit API key guide covers setup in more detail.
Disabling withdrawals does not prevent losses through trading. A bot with trading access can make unfavorable trades, repeatedly spend fees, buy illiquid assets or use more of the available capital than intended. Nor does disabling Withdraw prove that every type of transfer is disabled: inspect the complete permission set.
3. Restrict access by IP and limit available capital
An IP whitelist limits use of a key to specified source addresses. For a cloud bot, you need the actual outgoing IP addresses of the servers making exchange requests. Your phone's IP or the website's address is not automatically the right one. Obtain current addresses through the product's official connection instructions.
Ask how a server address change is announced and handled. Requests from a new, unlisted address can fail until the restriction is updated. Do not remove the whitelist merely to make a connection work. It also cannot protect you from a compromised server that already has an allowed address.
A separate subaccount or limited trading budget can reduce the capital accessible to a strategy. Its usefulness depends on the exchange, account type and the bot's actual support. Confirm those details before relying on isolation. A budget field in an application is not necessarily an exchange-enforced access boundary: ask whether the key can still reach other available funds. Check key status and expiry conditions in the current exchange settings rather than assuming a universal lifetime.
4. Ask how credentials and administrative access are protected
API Key, API Secret and an RSA private key are different things. An API Key identifies the connection; the secret or private signing key, depending on the authentication method, enables request signing. Signing proves the authenticity of a request; it does not encrypt the whole service.
A useful explanation of key storage should answer practical questions:
- Where is the secret stored, and which people or processes can use it?
- How are the database, backups and support exports protected?
- How are secrets kept out of logs, error messages and diagnostic attachments?
- Who has administrative access, and how is that access limited?
- How do you remove the connection, and what happens to stored copies?
- What is the response process if a key may have leaked?
HTTPS protects a network connection. A .env file is a way to supply configuration. “AES-256” names an encryption algorithm. None alone proves protection of a working service: access to encryption keys, backups, logs and the running process also matters. If a server signs requests, a claim that its operator can never access the secret needs architectural evidence.
Use the product's documented connection flow. A Telegram integration or a private bot chat does not by itself prove end-to-end encryption or that a key stays on your device. Never send secrets to public groups, comments, unsolicited “administrators” or third-party security-check forms. Support should be able to discuss a problem using redacted information; this article has no credential input fields.
5. Understand what the trading algorithm actually does
You should be able to describe the strategy before allowing it to trade. Ask the developer to explain:
- What triggers the first purchase, and when does the bot sell?
- How is each order's size calculated, and how are fees accounted for?
- Does it average down, how is the reserve spent, and how much capital can it ultimately use?
- What limits apply to purchases and open orders?
- What happens during a long decline or when funds for the next action run out?
- Which decisions or recovery steps require your participation?
Ask for a simple falling-market example with your intended settings. It can reveal whether “small purchases” eventually consume the full reserve or whether a stated profit target ignores costs. If the explanation changes between marketing, documentation and support, resolve the difference before connecting.
Publishing the full source code is not required to explain behavior clearly. Open code is useful evidence, but does not by itself prove that a hosted version matches it or is operated securely. “Unique AI,” “secret algorithm” and “the bot decides everything” do not explain trading rules or limits.
6. Check what happens when execution fails
The practical question is: what happens to my trading if the exchange, network, bot server or control interface stops working? Ask for the documented behavior, known limitations and relevant test evidence. A promise of “24/7 operation” does not answer it.
- Partial fills: does the bot track the quantity actually bought or sold and the remainder?
- Timeouts and retries: does it establish the original order's outcome before trying again, with protection against an unintended duplicate?
- Lost connection and restart: does it reconcile actual exchange orders and executions before resuming?
- API limits: does it pace requests and handle limits rather than retry continuously?
- Notifications: what will you receive when fresh account data or normal operation cannot be confirmed?
An exchange accepting an order-creation request is a separate stage from a confirmed fill. Bybit's order acknowledgment does not itself prove execution. A timeout also does not prove that an order was never created. Check the API error and recovery guide for the difference between an access problem and an unknown order outcome.
Understand exactly what STOP means
Stopping new operations, cancelling open orders, selling assets already purchased and revoking the API key are four different actions. A button named STOP does not establish that it performs all four. Ask which actions continue after a stop, what orders remain at the exchange and how to check them. Revocation ends the key's ability to authorize future API requests; it is not confirmation that existing orders were cancelled or assets sold.
7. Set limits for the trading risk that remains
Even with secure access and correct execution, an asset can fall sharply. Low liquidity can make an exit difficult; slippage is the difference between the expected and actual execution price. Capital may remain tied up in positions, an averaging reserve may run out, and concentration in one coin can magnify a loss. The exchange itself can restrict operations or suffer an outage.
Ordinary Spot trading without borrowing, margin trading and derivatives have different risk structures. Owning an unleveraged Spot asset removes neither its price risk nor the possibility of losing the capital committed to it. Do not assume a protective order will obtain its target price in all market conditions.
Before connecting, write down the allocated budget, the loss you are prepared to bear, maximum exposure to one strategy, the conditions for stopping new purchases and your plan if the market does not recover for a long time. Check how each limit is implemented: an alert, a bot setting and an exchange order are different controls. There is no universal safe deposit or risk percentage. The averaging-down risk guide shows why a lower average entry price can still accompany a larger loss and a depleted reserve.
8. Count the full cost once
Separate exchange fees on buys and sells, the bid–ask spread, slippage, the service subscription, any performance fee and other applicable costs such as your own server. Ask which items are already included in each reported profit figure and which are paid outside the trading account.
Never subtract a fee twice if it is already included in profit. Conversely, a positive trading result may not cover the subscription. The spread and slippage affect execution prices; do not treat them as another invoice to the bot. For a planned round trip, the Spot trading fee calculator helps compare trading costs and break-even assumptions. Use your actual exchange fee tier and current service terms.
9. Read performance as a whole-account result
Establish what the figures represent: live trading, a demonstration, a backtest on historical prices or a hypothetical simulation. A backtest depends on its assumptions, data quality, costs and execution model; a demo cannot reproduce every condition of live trading.
Realized P&L comes from completed transactions. Unrealized P&L is the gain or loss on positions still open at the stated valuation. Both matter when assessing changes in the value of all capital assigned to a strategy. Deposits and withdrawals also change an account balance and must be separated from trading results.
A high percentage of profitable closed trades can coexist with large open losses. Many orders do not establish profit, a favorable short period may miss a prolonged decline, and a balance screenshot does not show starting capital or cash flows. Ask for the reporting period, capital used, deposits and withdrawals, open positions, all applicable costs, and gaps in order or execution data. Drawdown shows a decline from an earlier peak; check what account value and sampling method the report uses.
Over a hypothetical period, closed trades produced +100 USDT after trading fees. Open positions have unrealized P&L of −180 USDT. A subscription paid outside the trading account cost 20 USDT. The combined result is 100 − 180 − 20 = −100 USDT.
There are no other capital changes, cash flows or costs in this example. Trading fees are already included in the 100 USDT and are not deducted again. This is not TradeMatic performance or a forecast.
When historical records contain a result but lack complete fills or fee data, that history cannot be described as independently verified net performance. Ask what can be reconciled with exchange records and what remains incomplete. Past results do not guarantee future returns.
10. Check the developer and the evidence behind claims
Look for identifiable product authorship, working official contact channels, terms of use and a data policy. Read update notes and known limitations. A useful support response explains what is known, asks for safe diagnostic information and gives a practical next step. Check whether reviews can be verified and whether affiliates or the publisher disclose their commercial interest.
If an independent audit is claimed, find the auditor, date, scope, tested version and available report. A review of one component is not an audit of every production system. Domain age, follower counts, an attractive website and positive reviews are not standalone evidence of security; a new domain or small project alone is not evidence of fraud either.
Postpone connecting funds if you encounter guaranteed-return promises, pressure to deposit urgently, unexplained requests for broad permissions, demands for your seed phrase, exchange password or confirmation codes, no clear way to stop access, or contradictory performance and service terms. Apply these criteria to the product's actual statements without making unsupported accusations about competitors.
A practical checklist before connecting funds
Use one record for each product you compare. Mark a check as confirmed only when the evidence answers it. Information unknown — confirmation required is a separate status, not a pass. If an important point remains unclear, postpone the connection rather than convert the number of completed rows into a safety score.
| What to check | Where or how | Evidence to seek | When to postpone |
|---|---|---|---|
| 1. Control of capital | Trace the money through the documented operating model. | A clear account or wallet owner and return process. | The recipient or control of funds is unknown. |
| 2. Purpose of payment | Read the invoice and service terms. | Subscription, trading capital and other fees are distinguished. | A requested transfer has no clear purpose or terms. |
| 3. Developer and contact | Check authorship, official support, terms and data policy. | Consistent identity and functioning contact channels. | Basic responsibility or terms cannot be established. |
| 4. API permissions | Compare the saved exchange permissions with the stated need. | Only required rights; withdrawals, transfers and derivatives checked separately. | Extra rights are unexplained or permissions are unknown. |
| 5. Independent revocation | Find the key in exchange API Management. | You know how to revoke it without the bot's help. | The developer is the only proposed way to stop access. |
| 6. IP restrictions | Compare allowed IPs with official server addresses. | Verified outgoing IPs and an address-change procedure. | You are told to allow every IP to avoid errors. |
| 7. Accessible budget | Check account scope, bot limits and subaccount support. | The amount the key can reach and any isolation limits are clear. | A claimed budget boundary is unconfirmed. |
| 8. Secret storage | Read the security explanation; ask specific questions. | Storage location, authorized users/processes and removal process. | Only “HTTPS” or an encryption slogan is offered. |
| 9. Copies and administration | Ask about logs, backups, exports and administrator access. | Secret redaction, restricted access and incident handling are explained. | Secrets are requested in raw logs or public channels. |
| 10. Trading rules | Walk through a buy and sell example with your settings. | Triggers, order sizes, fees and user actions are understandable. | “AI” or secrecy replaces an explanation. |
| 11. Reserve and exposure | Review prolonged-decline and insufficient-funds scenarios. | Purchase limits, reserve use and maximum exposure are clear. | The response to an exhausted reserve is unknown. |
| 12. Failure recovery | Ask about partial fills, timeouts, restarts and API limits. | Reconciliation, duplicate prevention and alerts are documented. | Blind order retries or missing state checks are proposed. |
| 13. STOP behavior | Read the stop procedure and verify what stays on the exchange. | New actions, existing orders, positions and revocation are distinguished. | A stop button is presented as proof of all four actions. |
| 14. Market and instrument risk | Check Spot, borrowing, derivatives, liquidity and concentration. | A risk structure and personal loss plan you understand. | Leverage is hidden or losses are described as impossible. |
| 15. Full cost | Compare exchange fees, execution costs and service terms. | Included and external costs, renewal and performance fees are clear. | Profit cannot be understood without guessing about costs. |
| 16. Performance completeness | Review the period, capital, flows, open positions and data gaps. | Live/test labels, realized/unrealized P&L and cost treatment. | Only winning trades, screenshots or incomplete totals are shown. |
| 17. Reviews and audits | Find original reviews and any claimed audit report. | Verifiable scope, date, author and commercial disclosures. | Returns are guaranteed or an audit claim cannot be substantiated. |
| 18. Trial and onboarding | Read the supported demo and connection procedure. | You understand environment limits and the first real actions. | A demo is sold as proof of future returns or onboarding is unclear. |
Eight steps before the first connection
- Verify the product and developer. Use official contacts and read service and data terms.
- Understand the strategy and costs. Explain its buying, selling and reserve rules in your own words.
- Set a dedicated budget and limits. Decide your exposure, acceptable loss and prolonged-decline plan.
- Inspect the key's actual permissions. Grant only the required scope.
- Apply supported access restrictions. Confirm server IPs and any account isolation before relying on them.
- Find independent revocation. Know the exchange-side procedure and how to inspect standing orders.
- Study a demo if supported. Use the correct environment and learn its limitations; a demo or backtest is not proof of future live profit.
- Begin real use only after understanding the limits. Resolve critical unknowns and know what the first operation will do.
If you suspect a compromised key
Open the exchange through a verified address and revoke the suspicious API key yourself. Inspect open orders and recent fills, review the exchange account's security and active sessions, and preserve details of suspicious operations. Contact official support when necessary. Create a replacement key only after investigating the cause and securing the affected access.
Revocation does not establish that standing orders were cancelled or assets sold: check and manage them separately in the exchange account. Do not enable withdrawals or transfers for a supposedly convenient bot-side shutdown. You must be able to end API access from the exchange.
How to apply this checklist to TradeMatic
Apply the same requirements to this product as to any other. This article is published by TradeMatic’s developer. Reviewing current source and documentation for it is not an independent security audit or a test of real failures.
- Confirmed in current code: the trading path targets Bybit Global MAINNET Spot and UTA 2.0. It uses a market purchase and a GTC limit sale, without enabling borrowing in the order builder. BUY size is configured in USDT; additional buys are tied to the latest confirmed purchase. This guarantees neither a desired execution price nor market recovery.
- Access and secrets: the supported connection flow uses
/settingsin a private chat with the genuine @TradeMaticBot. The server processes the API Key and API Secret. This flow must not be described as end-to-end encryption or as keeping the secret only on the user’s device. - Stopping:
/stopprevents new entries and purchase continuations. Existing own lots and SELL obligations remain managed; an already-dispatched BUY may still need its SELL placed. This does not cancel every order, sell assets or revoke the key.
Stated in current instructions: trading funds remain in the user’s exchange account, and the subscription pays for access to the software. The recommended setup is a separate system-generated HMAC key with Read-Write and SpotTrade, without Withdraw or Transfer. Check the actual permissions in Bybit: a successful connection does not establish that every granted permission is necessary. See current pricing and terms. This article did not verify custody arrangements or an individual account’s permissions.
Confirmed statistics limitation: the public all-time Sales result combines actual calculations with stored historical values. Incomplete execution and fee data prevent the entire history from being described as independently verified net returns or as the performance of all exchange-account capital.
Not established by this review: protection of every production key and backup, technical inaccessibility of secrets to the operator, subaccount support, independent certification or guaranteed availability. A stop-loss, guaranteed loss cap or total strategy-capital cap is also not established. Seek separate confirmation before connecting if you require these properties. See the Telegram command guide for current controls.
Frequently asked questions
Can I lose money when API withdrawals are disabled?
Yes. Trading permissions still allow purchases and sales that can lose value, incur fees or concentrate capital in an illiquid asset. Check transfers separately too; the withdrawal switch is not a complete permission review.
Is a cloud bot or my own server safer?
Compare who can access credentials, who maintains the system and how failures are handled. Your own server gives you more operational responsibility. A cloud service requires evidence about its controls. The deployment model alone does not decide the result.
Why use an IP whitelist?
It limits where a key can be used. It is useful against use from unapproved addresses, but not against compromise of an allowed server. Get the server's real outgoing addresses and understand how changes are handled.
Is a high win rate enough?
No. Check the size of gains and losses, open positions, drawdown, costs and capital used over the same period. Profitable closed trades can conceal a falling overall account value.
How does STOP differ from revoking the API key?
STOP performs whatever actions the product documents. Revocation prevents the key from authorizing future requests at the exchange. Neither label confirms cancellation of all standing orders or sale of existing assets.
Can I trust a backtest?
Use it to examine a strategy under stated assumptions. Check costs, execution assumptions, data quality and periods of decline. It does not prove that live execution, access security or future returns will match.
What if the developer will not explain key storage?
Ask where credentials reside, who can use them, how copies are protected and how removal works. If those answers remain unavailable, record the status as unknown and postpone connecting funds.
What starting amount makes a connection safe?
There is no universal safe amount. Reducing the accessible budget can limit the size of a loss, but it does not make the system risk-free. Choose a budget from your own loss tolerance and the strategy's requirements after completing the checks.
Sources and scope
Sources checked on 20 November 2026. Bybit references concern Global; interface and applicability depend on account type. OWASP guidance helps frame questions about secrets and logs but does not verify a particular service. The CFTC advisory informs scrutiny of return promises, not the application of one jurisdiction’s legal requirements to every reader.