DEV Community: Bot LAB

Unclaimed ATOM staking rewards: why they do not arrive automatically

Bot LAB — Wed, 04 Nov 2026 10:06:28 +0000

If you stake ATOM, your rewards are not added to your wallet balance automatically. They build up and wait until you claim them. Seeing an unclaimed balance is completely normal, and it does not mean anything is stuck.

How to claim

Open a Cosmos wallet such as Keplr or Leap, go to staking and choose Claim all. Each claim costs a small fee, so claiming tiny amounts often is not worth it. Some people claim and restake once the amount is meaningfully larger than the fee.

Unclaimed rewards do not compound. Rewards only earn more once you claim them and delegate them again.

Do not confuse rewards with unbonding

Unbonding is different. When you undelegate ATOM, it goes through a 21-day waiting period. During that time it earns nothing and cannot be moved, then it returns to your balance automatically. No claim is needed for unbonded ATOM.

So there are three separate lines to look at: available ATOM, delegated ATOM, and unbonding ATOM, plus rewards on top.

Check your own wallet

See your ATOM delegations and rewards with StuckScan. It is free and read-only: you paste a public address, with no wallet connection and no signing. It shows what it checked on each chain, and anything it could not check is listed as such.

Never share your seed phrase or private key. Nobody legitimate needs them to help you, and BOTLAB never charges a fee to "recover" funds.

Want these checks run on your own strategy? See the strategy and backtest audit.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Bitcoin transaction stuck unconfirmed? What low fees do and how to fix it

Bot LAB — Wed, 04 Nov 2026 08:06:23 +0000

Miners pick transactions largely by fee rate, measured in sats per virtual byte. If yours pays less than others, it waits. Nothing has been lost: an unconfirmed transaction has not moved your coins yet.

Check it first

Paste the transaction ID into a mempool explorer and compare its fee rate with the current recommended rates. If it is close to them, patience is often enough. If it is far below, or below the minimum relay fee, it may wait a very long time.

Your options

Replace-by-fee (RBF): if you sent it and your wallet supports RBF, use "Bump fee" or "Speed up". This sends a replacement with a higher fee.
Child-pays-for-parent (CPFP): if you are the receiver, or the transaction has change returning to you, spend that unconfirmed output with a high fee. Miners then take both transactions together.
Wait for it to drop out: nodes eventually forget very old unconfirmed transactions, commonly after around two weeks, and your wallet can then let you try again.

Avoid this mistake

Do not resend the same payment from a different wallet while the first one is pending. If both confirm, you have paid twice. Be wary of paid "transaction accelerator" offers from strangers too.

Check your own wallet

Check a wallet for low-fee transactions with StuckScan. It is free and read-only: you paste a public address, with no wallet connection and no signing. It shows what it checked on each chain, and anything it could not check is listed as such.

Never share your seed phrase or private key. Nobody legitimate needs them to help you, and BOTLAB never charges a fee to "recover" funds.

Want these checks run on your own strategy? See the strategy and backtest audit.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

TRX unstaked and 14 days have passed: why you still need to withdraw

Bot LAB — Wed, 04 Nov 2026 08:06:21 +0000

Under TRON Stake 2.0, unstaking is not the last step. After you unstake, the TRX enters a 14-day waiting period. Once that ends, it does not return to your available balance by itself. You need to send one more transaction to withdraw it.

What to do

Open your wallet or Tronscan and connect the address that staked.
Find the Stake or Resources section.
Look for the unstaked TRX that has finished waiting, and choose Withdraw.

The transaction uses bandwidth, which most accounts already have, or a small amount of TRX.

Common questions

Do I lose anything by waiting? The amount does not disappear, but it earns no voting rewards while it sits there.

Can I cancel an unstake? Stake 2.0 has a function to cancel pending unstakes, and wallets vary in whether they offer it. Check your wallet's staking page.

Why does my wallet show less TRX than I expected? Frozen and unfreezing TRX is often shown separately from the available balance. Add those lines together before assuming anything is missing.

Check your own wallet

Check your TRX staking status with StuckScan. It is free and read-only: you paste a public address, with no wallet connection and no signing. It shows what it checked on each chain, and anything it could not check is listed as such.

Never share your seed phrase or private key. Nobody legitimate needs them to help you, and BOTLAB never charges a fee to "recover" funds.

Want these checks run on your own strategy? See the strategy and backtest audit.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Unstaked SOL not back in your wallet? Deactivated stake accounts explained

Bot LAB — Wed, 04 Nov 2026 06:06:28 +0000

Staked SOL sits in a separate stake account, not in your main balance. That is why unstaking does not put SOL straight back into your wallet. It takes two steps.

Deactivate. The stake winds down at the end of the current epoch, which lasts about two days.
Withdraw. You then move the SOL from the stake account back to your wallet.

If the second step never happens, the SOL stays in the stake account. It is safe, but it earns nothing and it does not appear in your spendable balance.

How to withdraw

Open the staking section of the wallet that controls the stake account, such as Phantom or Solflare, find the deactivated account and choose Withdraw. You pay a very small network fee.

Only the stake account's withdraw authority can do this. That is normally the wallet that created it, but it may not be if the stake came through an exchange or a custody service.

How to tell which state you are in

Active: earning rewards. Nothing is wrong.
Deactivating: wait for the epoch to end.
Deactivated: withdraw it whenever you like.
Not delegated: the SOL inside is idle and can be withdrawn.

You can look up stake accounts for your address on a Solana explorer.

Check your own wallet

Find your Solana stake accounts with StuckScan. It is free and read-only: you paste a public address, with no wallet connection and no signing. It shows what it checked on each chain, and anything it could not check is listed as such.

Never share your seed phrase or private key. Nobody legitimate needs them to help you, and BOTLAB never charges a fee to "recover" funds.

Want these checks run on your own strategy? See the strategy and backtest audit.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Lido withdrawal finalized but no ETH in your wallet? How to claim it

Bot LAB — Wed, 04 Nov 2026 06:06:27 +0000

A Lido withdrawal has two stages, and only the first happens by itself. After you request a withdrawal, the protocol finalizes it, usually within a few days. The ETH does not arrive in your wallet at that point. You still have to send a claim transaction.

That catches people out. The request looks finished, nothing arrives, and it is easy to assume something went wrong. In most cases the ETH is waiting for you, with no deadline to claim it.

How to claim

Open the official Lido app at stake.lido.fi and connect the wallet that made the request.
Go to Withdrawals, then Claim.
Select the finalized requests and confirm. You pay only the network fee.

Check the address carefully. Fake staking sites are common, so type it yourself or use a bookmark rather than following a link from a message.

What the status means

Pending: the request is in the queue. A few days is normal, and it can take longer when many people exit at once.
Ready to claim (finalized): the ETH is available. Claim it whenever you like.
Claimed: it is finished, and the ETH should be in the wallet.

While a request waits, its amount stops earning staking rewards, so there is little reason to leave a finalized request unclaimed.

Moved your withdrawal NFT?

A request is represented by an unstETH NFT, and whoever holds that NFT can claim. If you moved it to another wallet, claim from that wallet.

Small amounts

If the amount is very small, the network fee on Ethereum can be higher than what you would receive. Waiting for a quieter period can help.

Check your own wallet

Check for unclaimed Lido withdrawals with StuckScan. It is free and read-only: you paste a public address, with no wallet connection and no signing. It shows what it checked on each chain, and anything it could not check is listed as such.

Never share your seed phrase or private key. Nobody legitimate needs them to help you, and BOTLAB never charges a fee to "recover" funds.

Want these checks run on your own strategy? See the strategy and backtest audit.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Hyperliquid Trading Bot: What to Backtest First

Bot LAB — Wed, 04 Nov 2026 04:06:22 +0000

Before you trust a Hyperliquid trading bot, backtest its net result after fees, slippage and funding, then check whether that result survives on data the bot has never seen. If it does, run it in paper trading on live prices, because a backtest alone can't show how the bot handles real market conditions.

New bots and bold screenshots tend to appear wherever attention goes, so it helps to know how to test them. This guide makes no claim about where prices go next.

First, define what you are testing

"Hyperliquid trading bot" can mean two different things:

A bot that trades the HYPE token, on any venue that lists it.
A bot that executes on the Hyperliquid exchange, on any of its markets.

The two have different risks. The first depends on one asset's price history. The second depends on one venue's fees, funding, order books and technical limits. Write down the market, venue, timeframe and order type before you run any test, or your results may not apply to what you later run.

What to backtest first

1. Total trading costs

Start with costs, because they can end the test quickly. Model all three of these:

Fees: use the fee tier you would actually pay, and separate maker fees from taker fees. Many backtests assume limit orders always fill, which is rarely true.
Slippage: estimate this from order book depth at your intended order size, not from a flat guess. Depth can vary widely between markets and times of day.
Funding: perpetual futures charge or pay funding while a position is open. Funding intervals differ by venue, so check the current rules in the exchange docs, and don't reuse assumptions from another venue.

2. How much history you really have

HYPE has a relatively short price history, so it covers a limited number of market conditions. A short history creates two problems:

The bot may have learned one market phase rather than a repeatable pattern.
You have fewer independent periods to test against.

A strong result on one short period is weak evidence. Our guide on how many trades a backtest needs explains why sample size matters. Testing the same rules on other liquid markets can also help, though a good result there doesn't prove the bot will work on HYPE.

3. Out-of-sample and walk-forward results

Split your data before you tune anything. Optimise on one part and keep the later part untouched. Better still, use walk-forward testing: tune on a window, test on the next window, roll forward and repeat.

Look for these warning signs:

Most of the result comes from a few trades or one short stretch.
Small parameter changes turn a gain into a loss.
Out-of-sample results are far weaker than in-sample results.

4. How many versions you tried

If you test hundreds of parameter combinations and keep the best, its score is inflated by selection. Record every variant you run. The deflated Sharpe ratio is one way to adjust for this, and it only works if you count the attempts honestly.

5. Market exposure versus edge

A long-biased bot can look clever simply because the market rose during the test. Compare the bot with buy-and-hold over the same dates, and split its results into rising, falling and sideways periods.

If most of the return appears only when the market rises, the bot may just be carrying market exposure. For a coin that tends to move with BTC, also measure the correlation with BTC, because many of your "different" trades may be one bet.

6. Drawdown and liquidation

Maximum drawdown should be measured on a mark-to-market basis, including open positions, not just on closed trades. If the bot uses leverage, replay the worst periods with liquidation rules included. A backtest that ignores liquidation can show a position recovering when a real account would already have been closed out.

Worked example: how costs change the picture

Think of a bot's result as two layers. The gross result is what the entry and exit prices alone would have produced. The net result is what remains after fees on both sides of each trade, slippage on both sides, and funding paid for the hours a position stays open.

For a bot that trades often and holds for a few hours, each of those costs is small on its own, but they are charged on every trade, so they add up in the same way the gross edge does. A gross edge that looks healthy per trade can shrink to almost nothing once all three are subtracted, and the summed result over a whole backtest can shrink by the same proportion.

Now stress the test. Assume slippage is worse than your first estimate, as it would be in a thin market or a fast move, and leave everything else unchanged. If the bot's gross edge per trade is only slightly larger than its total costs, that single change can turn a small net gain into a net loss over the whole test.

The strategy didn't change. Only one cost assumption did, and that was enough to flip the outcome. A bot whose result depends that heavily on a cost assumption has very little margin for error, and you should treat its backtest as fragile until you have tested it with pessimistic costs.

Move to paper trading, and measure the gap

A backtest is a controlled replay. Paper trading uses live prices, simulated money and rules fixed in advance, so it can reveal problems a replay hides, such as signal delays, data gaps and bugs in how the bot runs.

Paper trading still has limits. Your simulated orders don't move the market, and fills can look better than they would in reality. Our guide to honest paper trading for crypto futures covers how to reduce this gap.

Set these rules before you start:

Fix the rules and parameters, with no tuning during the test.
Decide the minimum number of trades and the test length in advance.
Compare results with the backtest's trade frequency, average trade and drawdown.
Stop and investigate if the differences are larger than you expected.

What a high win rate can hide

Our own published data shows why a single number isn't enough. BOTLAB tracks bots against 6 statistical gates (G1–G6), defined on the site. All figures below are paper trading, meaning simulated money at real prices:

Combo4h-paper/blocked: 64 trades from 12 October to 3 November 2026, with a 75.0% win rate. It passed 5 of 6 gates, has the status "not ready", and its verdict is "market beta, no proven edge".
mr4h/long: 143 trades from 16 August to 4 November 2026, with a 72.7% win rate. It passed all 6 gates, and its verdict is still "sample too small to conclude".

Neither result says anything about how a bot would behave on Hyperliquid or HYPE, and neither predicts future results. They simply show that a high win rate doesn't settle the question.

To run a basic review of your own bot, try Check your bot. The BOTLAB platform page explains how we monitor and report on bots.

Practical checks beyond the backtest

Some risks won't appear in a price-based test:

Permissions: API keys should be trade-only, with withdrawals off and IP restrictions on where supported. On wallet-based venues, never give anyone your seed phrase or main private key. Use a delegated trading wallet if the venue offers one, and read its documentation first.
Technical failure: test what happens if the connection drops, an order is rejected or a rate limit is hit. Know how open positions get closed if the bot stops.
Venue risk: exchanges can change fees, margin rules and listings, and they can suffer outages. No backtest captures all of this.
Local rules: check whether a venue is available where you live, and follow the rules that apply to you.

FAQ

Can I backtest a Hyperliquid trading bot with free data?

Often, yes, at least for candle data, but candles alone are usually not enough. For realistic results, you also need historical funding rates and some estimate of order book depth. Check the data for gaps before you trust the output.

Are HYPE backtest results reliable?

They are limited by a relatively short price history. Treat them as one piece of evidence, and add out-of-sample tests, cost stress tests and a paper trading period.

How long should I paper trade a bot?

There is no fixed length. Set a minimum trade count in advance and try to include different market conditions. A slow bot needs far more calendar time than a fast one to produce the same sample.

Does a good backtest mean the bot will work live?

No. It only means the rules would have produced that result on past data under your assumptions. Live trading adds real fills, delays, outages and changing markets, and it can lose money.

Key takeaways

Define whether you are testing the HYPE token, the Hyperliquid venue, or both.
Model fees, slippage and funding first, then stress them.
Treat short history and heavy tuning as reasons for extra caution.
Compare results with buy-and-hold to separate market exposure from edge.
Paper trade with fixed rules before any live decision, and measure the gap against your backtest.

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Want these checks run on your own strategy? See the strategy and backtest audit.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Paper Trading Crypto Futures: How to Make It Honest

Bot LAB — Mon, 02 Nov 2026 04:06:22 +0000

Paper trading crypto futures means running a strategy or bot with simulated money on real market prices, so you can see how it behaves before risking capital. It is worth doing, but only if the simulation includes fees, slippage, funding payments and liquidation rules. Without those, a paper result will usually look much better than the same strategy would look live.

This guide shows how to set up an honest futures paper test, what to measure, and how to judge the result without fooling yourself.

Why paper trading crypto futures is harder than spot

Spot paper trading is simple: you buy, hold, and sell. Perpetual futures ("perps") add four costs and risks that many paper engines skip or simplify:

Funding payments. Perps charge or pay funding at set intervals. A bot that holds positions for hours or days can pay a meaningful amount here.
Leverage and liquidation. A paper engine that never liquidates you will hide your worst outcomes.
Taker fees on both sides. Many bots use market orders. Fees are charged on the full position size, not on your margin.
Slippage. Simulated fills at the last price ignore the spread and the order book, especially on fast candles and small coins.

If your paper tool ignores any of these, treat its numbers as an upper bound, not an estimate.

Paper trading crypto futures: a setup checklist

Before you start a paper run, decide what it must model. A good futures paper test should:

Use the exchange's real fee schedule for your account tier, maker and taker separately.
Add slippage per side. Even a small assumption (for example 0.02–0.10% per side, depending on the coin and order size) is better than zero.
Apply funding at the real intervals using historical or live funding rates for that contract.
Calculate a liquidation price for every position from your leverage and the maintenance margin rule, and close the trade if price touches it.
Use candle data the bot could actually see. Signals must use closed candles only, or you get look-ahead bias. See how to detect look-ahead bias.
Log every trade: entry, exit, size, fee, funding, and the reason for exit.

Decide your success rules before you start

Write down, in advance:

How many trades you need before you judge the result (more on this below).
The maximum drawdown you would accept.
What would make you stop the test early.

Setting the rules after you see the results is one of the most common ways traders talk themselves into a weak strategy.

Worked example: the paper vs live trading gap

Illustration only. These are made-up numbers to show the arithmetic. They are not results from any real bot.

Imagine a bot that opens 100 trades on a perp. Each trade uses 1,000 USDT margin at 5x leverage, so each position is 5,000 USDT notional. A basic paper engine (no costs) reports an average gain of +0.30% of notional per trade.

| Item | Per trade | 100 trades | |---|---|---| | Gross paper result (+0.30% × 5,000) | +15.00 USDT | +1,500 USDT | | Taker fees, assumed 0.055% per side (0.11% round trip) | −5.50 USDT | −550 USDT | | Slippage, assumed 0.05% per side (0.10% round trip) | −5.00 USDT | −500 USDT | | Funding, assumed 2 intervals × 0.01% paid | −1.00 USDT | −100 USDT | | Net after costs | +3.50 USDT | +350 USDT |

In this illustration, costs remove about 77% of the gross result. A small change in assumptions (say, slippage of 0.08% per side instead of 0.05%) would turn the net result close to zero. That is the paper vs live trading gap in one table.

Two lessons follow:

Costs scale with notional, not margin. Leverage makes every fee and slippage figure bigger relative to your capital.
Thin edges are fragile. If a strategy only survives with optimistic cost assumptions, it probably will not survive live.

For more on how funding interacts with strategy rules, see do funding rate and open interest filters improve a crypto bot.

What to measure during a futures paper test

Win rate on its own tells you little. Track these together:

Number of trades. Small samples can look great by luck. Our guide on how many trades a backtest needs covers sample size in detail.
Average result per trade after costs, in R (multiples of the planned risk) or in % of notional.
Profit factor: gross wins divided by gross losses, after costs.
Maximum drawdown, measured from peak equity, including open-position losses.
Liquidations and near-liquidations. Even one liquidation in a paper test is a serious warning.
Funding share. What share of total costs came from funding? A high share means holding time matters more than you thought.
Market exposure. If the bot is long most of the time in a rising market, its result may just be market direction (beta), not skill.

Compare paper fills with real prices

If you can, sample some paper trades and compare the simulated fill with what the order book actually offered at that time. If paper fills are consistently better, raise your slippage assumption.

How long should you paper trade futures?

There is no fixed number of days. What matters is the number of trades and the variety of market conditions. A bot that trades twice a week needs months to show anything; a bot that trades ten times a day may reach a useful sample sooner, but it also pays far more in fees.

A practical approach:

Run until you reach your pre-set trade count.
Make sure the period includes at least one strong move and one choppy, sideways stretch.
Judge the result only after costs, and only against the rules you wrote down at the start.

How we judge paper results

At BOTLAB, a bot is only marked "ready for micro live" after it passes 6 statistical gates (G1–G6), defined on the site. Most bots do not pass: of 221 bots tracked, 1 currently has that status and 219 are marked not ready.

Even a bot that passes needs care. In our published paper trading results, mr4h/long recorded 138 trades over 78 days (16 Aug to 2 Nov 2026, simulated) with a 72.5% win rate and passed all 6 gates, and our verdict is still "sample too small to conclude". That is the standard we suggest for your own tests: a good-looking number is a reason to keep testing, not a reason to go live. You can see how results are tracked on the platform page, and recent notes in Lab News such as Fees first.

If you already have trade logs from your own bot, you can run them through our free tool, Check your bot, to see how the numbers look after a basic statistical check.

Common mistakes in futures paper trading

Testing at high leverage "because it's paper". Paper trading should match the leverage you would actually use, or the test means nothing.
Ignoring funding on long holds. Swing-style bots on perps can pay funding many times per trade.
Restarting the test after a bad week. Resetting erases the drawdowns you most need to see.
Changing parameters mid-test. Each change starts a new test. Keep a log of every version.
Treating paper as proof. Paper trading removes real execution, queue position and emotional pressure. Live results can be worse.

FAQ

Can I paper trade crypto futures for free?

Yes. Many exchanges offer a testnet or demo mode for perps, and several charting and research platforms offer simulated accounts. Check whether the tool models funding, fees, slippage and liquidation before trusting its numbers.

Can I paper trade crypto perps through an API?

Often, yes. Exchange testnets usually expose the same API as the live venue, which lets you test a bot's order logic end to end. Testnet prices and liquidity can differ from the live market, so compare fills against live data where possible. When you later connect any bot to a live account, use a trade-only API key with withdrawals off and IP restriction on.

Is TradingView paper trading good enough for futures bots?

It is useful for practising manual entries and checking signals on charts. For bot testing, check whether it charges funding and applies realistic fees and slippage. If it does not, add those costs yourself using a spreadsheet like the table above.

Does bot trading work if the paper test is positive?

A positive paper test is one piece of evidence, not proof. It needs enough trades, realistic costs, a period with mixed market conditions, and a result that does not depend on market direction alone. Many strategies that look good on paper fail live. See crypto trading bot backtesting: an honest how-to guide.

Key takeaways

Paper trading crypto futures is only meaningful if it models fees, slippage, funding and liquidation.
Costs scale with notional size, so leverage magnifies them.
Set trade count, drawdown limits and stop rules before you start.
Judge results after costs, on enough trades, across different market conditions.
A strong paper result means "keep testing", not "go live".

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Want these checks run on your own strategy? See the strategy and backtest audit.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Crypto Trading Bots That Work: How to Tell Honestly

Bot LAB — Fri, 30 Oct 2026 04:06:22 +0000

People searching for "crypto trading bots that work" usually want a name, but no bot "works" in general. A bot only works if it shows a measurable edge after fees and slippage, over enough trades, in conditions it did not see during design, and most bots fail that test. This guide shows you how to run that test yourself, so you can judge any bot, including one you built, bought or found online.

What "a crypto trading bot that works" actually means

A bot that works is not one with a nice screenshot or a high win rate. It is a bot whose results survive four questions:

Is there enough data? A few dozen trades can look brilliant by pure luck.
Does it survive real costs? Fees, slippage and funding payments eat small edges first.
Is it more than market beta? A long-only bot in a rising market can look clever while simply riding the trend.
Does it hold up forward? Results on data the bot was never tuned on matter far more than the backtest.

If a bot cannot answer all four with evidence, you do not know whether it works. That is a fine place to be. It means you keep testing instead of risking capital.

Step 1: Check the sample size before anything else

Small samples are the most common reason people think a bot works when it does not. With 30 trades, a strategy with zero edge can easily show a 60% win rate.

Practical rules of thumb:

Under 50 trades: treat results as anecdotes.
100–300 trades: you can start to see patterns, but confidence intervals are still wide.
Several hundred trades across different market regimes (trend, range, high volatility): now the numbers begin to mean something.

Days matter as well as trades. A bot that made 300 trades in one week has seen one market regime. For more detail, see How Many Trades Does a Backtest Need?.

Step 2: Put real costs into every result

Many bots that "work" in a backtest are simply ignoring costs. Add all of these:

Trading fees on both entry and exit (taker fees if the bot uses market orders).
Slippage: the gap between the price the bot wanted and the price it got. It grows in thin markets and fast moves.
Funding payments on perpetual futures, which can run for or against you every few hours.
Spread on less liquid pairs.

Scalping and high-frequency bots are hit hardest, because costs are paid on every trade while the edge per trade is tiny.

Worked example: why a 70% win rate can still lose

The numbers below are a made-up illustration, not BOTLAB results and not results of any real bot.

Imagine a bot with these backtest stats over 100 trades:

Win rate: 70%
Average win: +0.8%
Average loss: −1.6%

Before costs (simple sum, ignoring compounding):

Wins: 70 × 0.8% = +56%
Losses: 30 × 1.6% = −48%
Gross result: +8%

Now add realistic costs per round trip:

Fees: 0.11% (0.055% each side)
Slippage: 0.10% (0.05% each side)
Total: 0.21% per trade × 100 trades = −21%

Net result: +8% − 21% = −13%.

The high win rate hid a poor ratio of average win to average loss, and costs did the rest. This is why you should judge a bot on expectancy and profit factor after costs, not on win rate alone. See Profit Factor vs Win Rate for Trading Bots.

Step 3: Separate edge from market beta

If Bitcoin rose strongly during the test period, almost any long-biased bot looks good. Ask:

How did the bot do compared with simply holding the asset over the same period?
Did it trade both directions, or only long?
How did it behave in the falling and sideways parts of the test?

If returns track the market almost one-to-one, the bot is mostly giving you market exposure with extra fees. That is not an edge.

Step 4: Check for overfitting

A bot with many tunable parameters can be fitted to almost any history. Warning signs:

Results collapse when you change a parameter slightly (for example, a 20-period moving average works but 18 and 22 do not).
The developer tested hundreds of variants and shows you only the best one.
Performance is concentrated in a few huge trades.

Tools that help: walk-forward testing, out-of-sample periods, and statistics that adjust for how many variants were tried, such as the deflated Sharpe ratio.

Step 5: Close the paper vs live trading gap

A backtest is a model. Paper trading on live candles is the next step, because it exposes problems a backtest hides: missed fills, late signals, API errors and data gaps. Paper trading uses simulated money at real prices, so it is still not live, but it is a much more honest filter than a backtest.

When you finally compare paper and live, expect live to be somewhat worse. The size of that gap tells you how realistic your cost assumptions were.

Step 6: Look at drawdown, not just return

Before trusting any bot, find:

Maximum drawdown: the largest peak-to-trough fall in equity.
Drawdown duration: how long it took to recover.
Worst losing streak: how many losses in a row.

Then ask whether you could sit through that without switching the bot off at the worst moment. A strategy you abandon mid-drawdown does not work for you, whatever the backtest says.

Crypto trading bots that work: red flags to avoid

Walk away, or at least dig much deeper, if you see:

Promises of fixed monthly returns or "guaranteed" profit.
Results with no trade count, no dates and no costs.
Only screenshots, no exportable trade log.
Pressure to deposit funds with the bot provider rather than using your own exchange account.
Requests for API keys with withdrawal permission. A bot needs trade-only keys, with withdrawals off and IP restriction on.

What honest results look like in practice

At BOTLAB, a bot is only labelled "ready for micro live" after passing all 6 statistical gates (G1–G6), defined on the site. Most bots do not pass.

As of 30/10/2026, BOTLAB tracks 212 bots in paper trading (simulated money, real prices): 1 is marked ready for micro live and 211 are not ready. The one that passed, mr4h/long, has 124 paper trades over 74 days (16/08/2026 to 29/10/2026) with a 71.0% win rate, and our own verdict is still "sample too small to conclude". Three Atlas trend bots, with 224–359 paper trades each over 78 days (08/08/2026 to 25/10/2026), passed only 2 of 6 gates, with the verdict "market beta, no proven edge". Publishing the losers is part of the method; see Day one: read the losers too.

That ratio is the honest answer to the search: bots that clearly work are rare, and even a bot that passes every test still needs forward data. You can read more about how bots are tested and monitored on the platform page. Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

If you have your own bot's trade history, you can run a first sanity check with the free tool: Check your bot.

A quick checklist you can use today

At least a few hundred trades across more than one market regime?
Fees, slippage and funding included?
Compared with simply holding the asset?
Tested out of sample or walk-forward?
Paper traded on live candles before any real money?
Max drawdown you could actually live with?
Trade-only API key, withdrawals off?

If any answer is "no" or "I don't know", the bot has not yet shown that it works.

FAQ

Are crypto trading bots worth it?

They can be useful for executing rules consistently and testing ideas, but that is different from being profitable. Whether one is worth it depends on evidence: trade count, costs, drawdown and forward results. Without that, you are paying for automation, not an edge. See also Is a Trading Bot Profitable?.

Trading bot vs human: who actually wins?

Neither wins by default. Bots are faster and do not panic, but they follow rules blindly when market conditions change. Humans adapt but break their own rules. The fair comparison is the same strategy, the same costs and the same period, judged on risk-adjusted results.

Is paper trading crypto useful before going live?

Yes. Paper trading on live prices catches execution problems, signal delays and unrealistic cost assumptions that backtests miss. It does not include real slippage or emotional pressure, so treat it as a filter, not proof.

What is a realistic trading bot success rate?

There is no fixed figure. A win rate means little without the average win, average loss and costs. Read Trading Bot Success Rate: What the Number Really Means for how to interpret it.

Key takeaways

No bot "works" in general; it either shows a tested edge after costs or it does not.
Check sample size, real costs, market beta and overfitting before trusting any result.
A high win rate can still lose money once fees and slippage are included.
Paper trade on live candles before risking capital, and expect live results to be worse.
Use trade-only API keys with withdrawals off, and avoid anyone promising fixed returns.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Want these checks run on your own strategy? See the strategy and backtest audit.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Solana Trading Bot: What to Backtest First

Bot LAB — Wed, 28 Oct 2026 04:06:22 +0000

Before you run a trading bot on Solana, backtest three things first: whether the strategy survives realistic fees, slippage and funding, whether it holds up across different volatility regimes, and whether it has enough trades to mean anything. A SOL bot that looks good on a clean chart often fails one of these tests, so check them before you spend time on settings.

Solana is getting a lot of attention today, and attention like this often draws new bot users. This guide does not predict where SOL goes next. It shows how to test a bot on a coin that is getting a lot of attention, so you can judge it on evidence instead of excitement.

Why Solana needs its own backtest

A strategy that worked on BTC will not automatically work on SOL. Three differences matter:

Higher volatility. Altcoins like SOL usually move more than BTC in percentage terms. Stops get hit more often, and leverage hurts faster.
Beta to BTC. SOL often moves with BTC, but more sharply. A bot that "wins" on SOL may simply be riding BTC's direction with extra risk on top. That is market beta, not an edge.
Attention spikes. When a coin trends, spreads, funding rates and order-book depth can change quickly. A backtest built on quiet weeks may not describe a busy one.

So treat a SOL bot as a new strategy, even if the logic was copied from a BTC bot.

Step 1: Price in every cost

Most bot backtests fail here. Gross results ignore what you actually pay.

Trading fees

Use your exchange's real taker and maker fees for USDT perpetuals, and count both entry and exit. If your bot uses market orders, assume taker fees on both sides.

Slippage

Your fill price is rarely the candle close. Model slippage as a percentage per side and make it pessimistic. Then rerun with double that slippage. If the result collapses, the edge was too thin to be real.

Funding

On perpetual futures, longs and shorts pay each other funding, usually every 8 hours. Funding can rise during trending periods. A bot that holds positions for days can lose a noticeable share of its gross result to funding alone. Use historical funding data for SOL perps, not a flat guess.

Step 2: Split the history into regimes

A single backtest number hides how the bot behaved in different market conditions. Cut your SOL history into periods and test each one separately:

Strong uptrend
Strong downtrend
Sideways and choppy
High-volatility spikes (days when SOL or BTC moved sharply)

A trend-following bot will often look good in the first two and bleed in the third. A mean-reversion bot is often the opposite. Neither is "bad", but you need to know which conditions the bot depends on.

Also compare the bot to simply holding SOL over the same period. If the bot only makes money when SOL rises, and loses when SOL falls, it may be giving you leveraged exposure to SOL rather than a strategy.

Step 3: Check the sample size

Twenty trades on a trending coin prove very little. Results from small samples swing wildly by chance. As a rough rule, you want enough trades across several regimes before drawing conclusions. We go deeper on this in How Many Trades Does a Backtest Need?.

If you tested many parameter combinations to find the "best" one, the best result is inflated by luck. The Deflated Sharpe Ratio is one way to adjust for this.

Step 4: Rule out backtest errors

Before trusting any number, check for:

Look-ahead bias: the bot uses information it could not have known at the time (for example, a candle's close before it closed). See How to Detect Look-Ahead Bias in Your Own Backtest.
Survivorship bias: testing only on coins that are popular today. SOL is trending now; that tells you nothing about how the bot would have picked coins in the past.
Unrealistic fills: limit orders assumed to fill whenever price touches them.

Worked example: how costs change a SOL bot

Illustration only. These are made-up numbers to show the arithmetic. They are not BOTLAB results and not a forecast for SOL.

Imagine a SOL perpetual bot with this backtest:

80 trades
Average gross result: +0.35% per trade (on position size)
Average holding time: 16 hours

Now add costs per round trip:

| Cost | Per trade | |---|---| | Fees (0.055% taker × 2 sides) | 0.11% | | Slippage (0.05% × 2 sides) | 0.10% | | Funding (0.01% per 8h × 2 periods, if paying) | 0.02% | | Total cost | 0.23% |

Net result per trade: 0.35% − 0.23% = +0.12%. Costs took about two thirds of the gross result.

Now stress-test it. During a busy, trending week, assume slippage doubles to 0.10% per side (0.20% per trade) and funding doubles to 0.04%:

Total cost: 0.11% + 0.20% + 0.04% = 0.35%
Net result per trade: 0.35% − 0.35% = 0.00%

The same bot is now flat before any bad luck. If a modest cost increase wipes out the edge, the edge is too thin to rely on.

What leverage does to this

At x10 leverage, a 10% move against your position is roughly a full loss of the margin on that trade, before fees. Large single-day moves are common in altcoins. Any leverage setting should be tested in the backtest against the worst historical moves, not the average ones.

Step 5: Paper trade forward before anything else

A backtest is a story about the past. Paper trading (simulated money, real live prices) tests the bot on data it has never seen, with real-time spreads and timing.

Run the SOL bot in paper mode for enough trades to cover at least a couple of different market conditions. Compare the paper results with the backtest:

Is the win rate similar?
Is the average trade close to the backtest after costs?
Are drawdowns deeper than the backtest suggested?

A large gap between backtest and paper results usually means the backtest was too optimistic.

How we judge bots at BOTLAB

We hold every bot to 6 statistical gates (G1–G6), defined on the site, and a bot is only marked "ready for micro live" after passing all six. Out of 209 bots tracked, 1 currently has that status and 208 are not ready. For example, our bot mr4h/long passed 6 of 6 gates in paper trading (simulated) from 16 Aug to 28 Oct 2026, with 121 trades and a 70.2% win rate, and our verdict is still "sample too small to conclude". Three Atlas trend bots, with 224 to 359 trades each in paper trading (simulated) from 8 Aug to 25 Oct 2026, were judged "market beta, no proven edge". We publish the bots that fail our gates as well as the ones that pass. You can see how the tools fit together on the platform page. All paper results are simulated.

If you already have a bot's trade history, you can run it through our free tool: Check your bot.

FAQ

Is a Solana trading bot profitable?

There is no general answer. Some strategies have made money on SOL in some periods and lost in others. The only honest way to judge a specific bot is a cost-aware backtest across several regimes, followed by forward paper trading. Even then, past results do not predict future results.

Should I use the same settings on SOL as on BTC?

Not without testing. SOL usually moves more than BTC, so stop distances, position size and leverage that suit BTC can be too tight or too risky on SOL. Backtest SOL separately.

Do BTC moves matter for a SOL bot?

They can. SOL often moves with BTC, so a bot's SOL results may partly reflect BTC's direction. Test how your bot did on days when BTC moved strongly in each direction, and check whether the bot adds anything beyond simply holding SOL.

How long should I paper trade a SOL bot?

Long enough to collect a meaningful number of trades across more than one market condition. A single trending week is not enough, because quiet and choppy periods often behave very differently.

Key takeaways

Test fees, slippage and funding first, then stress-test them at double the cost.
Split SOL history into trend, chop and spike regimes; know which ones your bot needs.
Compare the bot with simply holding SOL to separate edge from beta.
Small samples and heavy parameter searches inflate results.
Paper trade forward before trusting any backtest.
Crypto trading can lose money, including all capital.

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Want these checks run on your own strategy? See the strategy and backtest audit.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Grid Trading Bot Backtest: How to Test One Honestly

Bot LAB — Mon, 26 Oct 2026 04:06:21 +0000

A grid trading bot backtest is only useful if it models how grid orders actually fill, charges every fee and funding payment, and includes the moment price leaves your range. Most grid backtests look smooth because they skip at least one of those, so the honest test is less about the profit line and more about what happens at the edges.

This guide shows how to backtest a grid bot properly, where grid backtests usually lie, and how to read the result before you risk real money.

What a grid trading bot backtest has to prove

A grid bot places buy orders below the current price and sell orders above it, at fixed spacing. Each time price drops to a buy level and then rises back to the next sell level, the bot completes a "round trip" and books a small gain.

That design makes two promises your backtest must check:

In a range: many small round trips add up to more than fees.
Out of a range: the losses from holding inventory while price trends away do not erase everything the range earned.

A backtest that only shows the first part is half a test. Grid bots tend to look excellent in sideways data and fail in trending data, so the question is never "did it make money in this window?" but "what did it do in the windows it was not designed for?"

How to run a grid trading bot backtest step by step

1. Use data fine enough to see the fills

Grid levels are often 0.5–2% apart. On 1-hour or 4-hour candles, price can touch several levels inside one bar, and you cannot know the order in which it touched them.

If a single candle's high and low cross both a buy level and the sell level above it, a naive backtest books a full round trip. In reality the order may have been sell-first, or only one side filled.
Use 1-minute candles or trade data where you can. If you only have coarse candles, adopt a conservative rule: at most one fill per level per bar, and never a buy and its matching sell in the same bar.

2. Define a realistic fill rule

A limit order "touched" is not a limit order "filled". There is a queue in front of you.

Count a buy as filled only if price trades through the level (for example, one tick below), not just to it.
Run the test twice: once with touch-fills and once with trade-through fills. If the result collapses under the stricter rule, the edge was in the fill assumption, not the strategy.

3. Charge every cost

Grid bots trade a lot for small gains, so costs decide the outcome.

Fees: use your real maker and taker rates, both sides of every round trip. If some of your orders end up as taker (re-entries, stop-outs, market rebalances), charge taker for those.
Slippage: small on limit fills, real on any market order, especially exits during fast moves.
Funding: if you run a grid on perpetual futures, inventory held across funding times pays or receives funding. In a long trend against you, this adds up quietly. Include it from historical funding data, not an average guess.

4. Pick the range without peeking

This is the most common hidden bias in grid backtests. If you look at a chart, see that price stayed between two levels for three months, and then set your grid to exactly that range, you have used future information. Of course it worked: you drew the box around the answer.

Instead, set the range with a rule that only uses past data at the time, for example "range = last 30 days' high and low, recalculated weekly". Our guide on detecting look-ahead bias covers more ways this sneaks in.

5. Decide what happens at the edges

Your backtest must include an explicit rule for when price leaves the grid:

Stop the bot and close inventory at a loss?
Hold inventory and wait?
Shift the grid to follow price?

Each choice gives a very different equity curve. Whatever you choose, test it as part of the strategy, not as an afterthought.

6. Cover more than one market regime

Include at least one strong uptrend, one strong downtrend and one sideways period. A single calm month is a sample of one regime, as we put it in One sunny week isn't a climate.

Worked example: why the edges matter

Illustration only. These are made-up round numbers to show the arithmetic. They are not BOTLAB results and not a forecast.

Imagine a spot grid on a coin priced at 100 USDT:

Range 90 to 110, levels every 2 USDT (about 2% apart).
1,000 USDT split into 10 orders of 100 USDT each.
Fee 0.1% per side.

Inside the range. One round trip on a 100 USDT order with a 2-point gap earns about 2 USDT gross. Fees on both sides cost about 0.20 USDT. Net is about 1.80 USDT. If the backtest shows 40 round trips in a month, that is roughly 72 USDT net.

Then price breaks down to 80. Five buy orders filled on the way down, at 98, 96, 94, 92 and 90. At a price of 80, each is now worth less:

| Buy price | Loss at 80 (per 100 USDT order) | |---|---| | 98 | about 18.4 USDT | | 96 | about 16.7 USDT | | 94 | about 14.9 USDT | | 92 | about 13.0 USDT | | 90 | about 11.1 USDT | | Total | about 74 USDT |

One move of 20% wipes out the whole month of round trips, before any slippage on an exit. If this were a leveraged futures grid, the same move could hit liquidation and add funding costs.

The lesson: a grid backtest that ends while price is still inside the range is showing you the 72 USDT and hiding the 74.

How to read the results honestly

Trade count overstates your sample

A grid bot can log hundreds of round trips in a few weeks. That looks like a big sample, but those trades are highly correlated: they all depend on the same thing, price staying in the range. Three hundred round trips inside one sideways month are closer to one observation of "sideways market" than to 300 independent tests. See how many trades a backtest needs for why the number of independent outcomes matters.

Win rate will look high, and mean little

Grid bots close winners often and hold losers as open inventory. A 90% win rate on closed trades can sit next to a large unrealised loss. Always judge on:

Equity including open positions, marked to market every bar.
Maximum drawdown, including unrealised losses.
Profit after all costs, divided by the worst drawdown.

Check for overfitting

If you tested 50 combinations of range width, grid count and spacing, then the best one will look good partly by luck. Signs of overfitting:

Results change sharply when you move spacing slightly (say 1.8% vs 2.0%).
The best settings differ a lot between one year and the next.
Performance depends on one or two big trending bars landing at the right moment.

Use walk-forward testing: choose settings on one period, then test them unchanged on the next. Our honest backtesting guide walks through the process.

Then forward test on paper

A backtest is a hypothesis. The next step is paper trading on live prices for long enough to see a range break, then comparing paper fills with what the backtest predicted. The gap between them, from fills, latency and fees, is information you cannot get from historical data.

How we judge bots at BOTLAB

We run every bot through 6 statistical gates (G1–G6), defined on the site, and publish paper trading (simulated money, real prices) results, losers included. Of 204 bots tracked as of 26 Oct 2026, 202 are NOT_READY. One, mr4h/long, has passed all 6 gates with 110 paper trades between 16 Aug and 26 Oct 2026, and even there our verdict is "sample too small to conclude". That is the standard we suggest for any grid bot: passing tests is a reason to keep watching, not proof of an edge.

If you already have a bot's trade log, you can run it through our free tool: Check your bot. Details of the hosted software and plans are on /platform.

FAQ

Is a grid trading bot profitable?

It can make money in ranging markets and lose money in trending ones, and nobody can know in advance which regime is coming. A backtest can tell you how the bot behaved in past regimes after costs. It cannot tell you future results. Our article on whether a trading bot is profitable explains how to test that question.

Can I backtest a grid bot for free?

Yes. You can use free historical candle data and a spreadsheet or open-source backtesting library, as long as you apply strict fill rules and real fees. Free paper trading on live prices is a good second step before any real money.

What is the best grid trading bot strategy?

There is no single best setting. A useful grid strategy is one whose range rule, spacing and exit rule survive walk-forward testing across several regimes, with acceptable drawdown when price leaves the range. Be cautious of any setting that only works on one period.

Should a grid bot use spot or futures?

Futures add leverage, funding costs and liquidation risk, which a backtest must model explicitly. Spot grids avoid liquidation but still carry inventory risk when price trends down. This is a general description, not a recommendation for your situation.

Key takeaways

A grid trading bot backtest must model fills, fees, slippage and funding, or it will overstate results.
Set the range with a rule that only uses past data; drawing the range on a chart is look-ahead bias.
Always test what happens when price leaves the range; that is where grid losses come from.
Hundreds of grid trades in one regime are not a large independent sample.
Judge on equity including open positions and max drawdown, then forward test on paper.

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Want these checks run on your own strategy? See the strategy and backtest audit.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Crypto Trading Bot Backtesting: An Honest How-To Guide

Bot LAB — Fri, 23 Oct 2026 04:06:21 +0000

Crypto trading bot backtesting means running a bot's rules over past market data to see how it would have traded, before you risk any money. Done honestly, it does not tell you whether a bot will make money. It tells you whether a bot is worth testing further, and most bots fail that test.

This guide shows how to run a backtest that is hard to fool: realistic costs, enough trades, data the bot never saw, and a forward test on live prices.

What crypto trading bot backtesting can and cannot tell you

A backtest replays history. It can show:

How often the rules would have traded
How large the losing streaks and drawdowns could get
How sensitive results are to fees, slippage and funding
Whether the edge holds across different coins and time periods

It cannot show:

How the bot behaves in market conditions that never appeared in your data
Your real fills during fast moves or thin order books
Whether the edge was real or a pattern you found by trying many settings

A backtest is the first filter, not the final verdict.

Why most crypto bot backtests look better than reality

1. Costs are missing or too small

Many tools default to zero fees and perfect fills. On perpetual futures you pay a trading fee on every entry and exit, you lose some price to slippage, and you pay or receive funding every few hours while a position is open. A strategy that trades often can turn from positive to negative once these are included.

2. Overfitting

If you test 200 combinations of moving-average lengths and pick the best one, that "best" result is partly luck. The more variants you try, the better the top one looks by chance. The deflated Sharpe ratio is one way to correct for this; see Deflated Sharpe Ratio Explained.

3. Look-ahead bias

The bot uses information it would not have had at the time. A common example is acting on a candle's close while it is still forming. Our guide on how to detect look-ahead bias in your own backtest walks through the checks.

4. Too few trades

Twenty trades with a 70% win rate can easily be noise. You need enough trades for the result to be distinguishable from luck; see How Many Trades Does a Backtest Need?.

5. One market regime

A trend bot tested only during a strong rally will look excellent. That may be market beta (the coin went up), not skill. Always compare against simply holding the asset over the same period.

A step-by-step backtesting process

Step 1: Write the rules down before you test

State entry, exit, stop, position size and which coins and timeframes the bot trades. If you change the rules after seeing results, record every change. Each one counts as another attempt.

Step 2: Use clean, realistic data

Use the exchange's own candles for the instrument you will trade (spot vs perpetual prices differ).
Check for gaps, duplicate candles and exchange outages.
For perpetuals, include historical funding rates.

Step 3: Model costs pessimistically

Taker fee on both sides unless you are sure your orders rest as maker
Slippage per trade (larger for small-cap coins and fast moves)
Funding for every interval a position is held
If your account is funded in USDT, include any conversion or withdrawal costs you actually pay

If the strategy only works with costs set to zero, it does not work.

Step 4: Split your data

In-sample: where you design and tune the rules
Out-of-sample: a later period you do not touch until the rules are frozen
Walk-forward: repeat tune-then-test across rolling windows

If out-of-sample results collapse compared with in-sample, assume overfitting.

Step 5: Measure more than total return

Look at:

Number of trades and test period
Win rate together with average win and average loss (see Profit Factor vs Win Rate)
Maximum drawdown and the longest time spent under a previous peak
Result versus buy-and-hold over the same dates
Result per coin and per year, not only the total

Step 6: Stress test

Double your slippage estimate
Shift entries by one candle
Nudge each parameter by 10–20%
Remove the single best trade

A robust strategy degrades gradually. A fragile one falls apart.

Step 7: Forward test on paper

Run the frozen rules on live prices with simulated money. This is where the paper vs live trading gap starts to show: missed fills, latency, and conditions the backtest never saw. Only forward results should change your opinion of a bot.

Worked example: what costs do to a scalping bot

Illustration only. These are made-up numbers to show the arithmetic. They are not BOTLAB results and not a real bot.

A bot on a 5-minute chart shows this backtest with zero costs:

600 trades over 3 months
Average gross result per trade: +0.10% of position size

That looks like a steady edge. Now add realistic costs per round trip:

| Cost item | Per round trip | |---|---| | Taker fee, entry + exit (0.055% each) | 0.110% | | Slippage (0.015% each side) | 0.030% | | Average funding while held | 0.005% | | Total cost | 0.145% |

Net result per trade: 0.10% − 0.145% = −0.045%.

Across 600 trades, before compounding, that is roughly 600 × −0.045% = −27% of position size. The same rules that looked profitable now lose money. Nothing about the signal changed, only the honesty of the cost model.

The lesson: the more often a bot trades, the bigger its edge per trade must be to survive costs.

How we apply this in practice

BOTLAB uses 6 statistical gates (G1–G6), defined on the site, that a bot must pass before it is considered for anything beyond paper trading. Most bots do not pass.

Our published results include the losers. For example, in BOTLAB paper trading (simulated money, real prices), Atlas/donchian-20d made 353 trades between 2026-08-08 and 2026-10-23 with a 41.6% win rate, and our verdict was "market beta, no proven edge". In other words, it mostly followed the market rather than showing skill. We wrote it up in Graveyard story: Atlas/donchian-20d. Paper results are simulated, and past results do not predict future results.

If you already have a backtest or trade log, you can run it through the free Check your bot tool to see common warning signs, or read more about how the research platform works on /platform.

Common mistakes checklist

Before you trust a backtest, ask:

Are fees, slippage and funding all included?
Is there an out-of-sample or walk-forward period?
How many variants did I try before picking this one?
Are there enough trades to separate skill from luck?
Does it beat buy-and-hold over the same dates, after costs?
Does it survive small parameter changes?
Has it been forward tested on live prices?

If you answer "no" or "not sure" to several of these, the backtest is not evidence yet.

FAQ

Is there free trading bot backtesting software?

Yes. Many charting platforms and open-source libraries let you backtest for free. The tool matters less than the method: check that it lets you set fees, slippage and funding, and that you can hold back an out-of-sample period.

How do you backtest a grid trading bot?

Grid bots need a fill model at every grid level, fees on each small trade, and a test across trending periods, not only sideways ones. Grids often look smooth in ranges and then carry large losses when price breaks out of the range and keeps going. Include that scenario in your data.

Does bot trading work?

Some rule-based strategies have shown an edge for a while; many have not. A bot is a tool that executes rules. If the rules have no edge after costs, automation only loses money faster. Test honestly and expect most ideas to fail. Our guide Is a Trading Bot Profitable? How to Test One Honestly goes further.

Is a Python trading bot backtest more accurate?

Not automatically. Writing your own backtester gives control, but it also makes look-ahead bias and cost mistakes easier to introduce. Validate it against a few trades you can calculate by hand.

Key takeaways

Crypto trading bot backtesting is a filter, not a forecast.
Include fees, slippage and funding, pessimistically.
Count every variant you tried; overfitting grows with each one.
Use out-of-sample data, walk-forward tests and stress tests.
Compare against buy-and-hold to separate edge from market beta.
Only forward paper results on live prices should change your view of a bot.

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.

Chainlink Trading Bot: What to Backtest First

Bot LAB — Wed, 21 Oct 2026 04:06:22 +0000

Before you run a trading bot on Chainlink (LINK), backtest three things first: whether the strategy survives realistic fees, slippage and funding costs, whether it has enough trades to mean anything, and how deep its worst drawdown gets. A coin being in the news changes how many people watch it. It does not change how you should test a bot.

Chainlink is on today's trending list, and attention brings a familiar urge: point a bot at the hot coin and see what happens. This guide shows what to check before any bot gets near a real account. It says nothing about where LINK's price is heading, because a testing guide can't tell you that and shouldn't try.

Why a trending coin needs more testing, not less

When a coin trends, three things often change at once:

Volatility can change. A backtest built on calm months may not reflect a busier market, or the other way round.
Liquidity conditions shift. Spreads and order book depth on altcoin pairs can move a lot from one week to the next.
Your own bias grows. If you already expect a move, you are more likely to accept a backtest that agrees with you.

The rule is simple. Test the strategy as if the coin were boring. If the logic only works because of recent excitement, you have learned about the news, not about your bot.

Step 1: Put real costs into the backtest

Most altcoin bots that look good on paper fail here first. A backtest without costs is a sketch, not a test.

Fees

Count the fee on every entry and every exit. Use taker fees unless you have proof your orders fill as maker. Market and stop orders are usually taker.

Slippage

Slippage is the gap between the price your backtest assumed and the price you would actually get. On a mid-cap pair it is often larger than on BTC or ETH, and it tends to be worst exactly when the bot wants to trade: on fast candles and breakouts.

A practical check: rerun the backtest at 2x and 3x your slippage estimate. If the result flips from positive to negative, the edge is too thin to trust.

Funding cost on perpetuals

If the bot trades perpetual futures, it pays or receives funding while positions are open. Bots that hold for hours or days can lose a meaningful share of their gross result to funding. Model it from historical funding data rather than assuming zero. For more on funding-based filters, see Do Funding Rate and Open Interest Filters Improve a Crypto Bot?.

Worked example: a LINK bot before and after costs

The numbers below are a made-up illustration to show the method. They are not BOTLAB results and not results of any real bot.

Imagine a short-term LINK perpetual strategy with this backtest:

140 trades over 60 days
Average gross result per trade: +0.14%
Win rate: 58%

That looks fine. Now add costs, per round trip:

Taker fee 0.055% on entry plus 0.055% on exit = 0.11%
Estimated slippage, both sides = 0.04%
Average funding paid while holding = 0.01%

Total cost per trade = 0.11% + 0.04% + 0.01% = 0.16%.

Net result per trade = 0.14% − 0.16% = −0.02%.

The win rate did not change, but the strategy went from "working" to slowly losing. This is why win rate alone tells you little; see Profit Factor vs Win Rate for Trading Bots. Leverage does not fix this. It multiplies both the gross result and the losses, and it brings liquidation risk closer.

Step 2: Check the sample size

A backtest with 25 trades can look excellent by luck alone. Before you trust any LINK result, ask:

How many trades? Dozens are rarely enough. A few hundred, spread over different market conditions, tells you much more. Our guide How Many Trades Does a Backtest Need? goes into the details.
How many conditions? Did the test include trending, falling and sideways periods, or only one regime?
How concentrated is the result? If removing the best 3 trades erases the profit, the bot depends on rare events.

Step 3: Look for overfitting

Overfitting means the strategy learned the noise in past data instead of a repeatable pattern. Trending coins invite it, because it is tempting to tune parameters until the backtest catches the recent move perfectly.

Warning signs:

Many parameters for a small number of trades
Results that collapse when a setting changes slightly (say, a 20-period lookback works but 18 and 22 do not)
You tried dozens of variants and are reporting only the best one

Fixes:

Out-of-sample testing. Tune on one period, then test on data the strategy never saw.
Walk-forward testing. Repeat the tune-then-test cycle across rolling windows.
Adjust for the number of attempts. If you tested 50 variants, the best Sharpe ratio is inflated. The deflated Sharpe ratio corrects for this.
Check for look-ahead bias, where the backtest accidentally uses information that wasn't available at the time: How to Detect Look-Ahead Bias.

Step 4: Measure drawdown before you look at the total

Total result is the number people share. Maximum drawdown is the number that decides whether you can live with the bot.

What was the deepest peak-to-trough fall in the backtest?
How long did it take to recover?
What would that drawdown look like with the leverage you plan to use?

Expect live drawdowns to be deeper than backtest drawdowns. Set a drawdown alert in advance, a level where you pause the bot and investigate, rather than deciding in the middle of a losing streak.

Step 5: Paper trade forward and compare

A backtest replays history. A forward paper test (simulated money, live prices) shows how the bot behaves on candles it has never seen. Then compare:

Paper fills vs backtest assumptions
Trade frequency vs backtest frequency
Drawdown vs backtest drawdown

The paper vs live trading gap is real. Paper trading still doesn't capture every partial fill, rejected order or API delay, so treat even good paper results as a starting point, not a conclusion.

How we apply this at the lab

At BOTLAB, every bot is judged against 6 statistical gates (G1–G6), defined on the site, and we publish the losers alongside the rest. One example from our published paper trading (simulated) results: Atlas/donchian-20d made 347 trades from 2026-08-08 to 2026-10-18, with a 41.8% win rate, and our verdict was "market beta, no proven edge". That is a useful lesson in itself: plenty of trades and a long period still did not show an edge beyond following the market. The full story is in Graveyard story: Atlas/donchian-20d.

Before you trust a strategy, you can run it through our free tool: Check your bot. To see how hosted bots and paper results fit together, visit the platform page.

Not available in restricted jurisdictions (see the Service Agreement). You trade with your own exchange account; BOTLAB never holds funds.

A quick pre-launch checklist for any LINK bot

[ ] Fees modelled as taker on every entry and exit
[ ] Slippage stress-tested at 2x and 3x
[ ] Funding included for perpetual positions
[ ] Enough trades across more than one market regime
[ ] Out-of-sample or walk-forward test done
[ ] Number of variants tested written down
[ ] Max drawdown known, and a pause level set
[ ] Forward paper test compared with the backtest
[ ] API key set to trade-only, withdrawals off, IP-restricted

FAQ

Is a Chainlink trading bot different from a BTC bot?

The testing method is the same. Practical conditions often differ: altcoin pairs can have wider spreads, thinner order books and different funding behaviour, so cost assumptions that worked on BTC may be too optimistic for LINK. Test each pair with its own data.

Should I backtest only the recent trending period?

No. A test limited to a period when the coin was in the headlines tells you how the bot did in one unusual window. Include quiet and falling periods as well, then check that results hold out of sample.

Can a high win rate make up for trading costs?

Not by itself. As the illustration shows, a bot can win most of its trades and still lose money once fees, slippage and funding are counted. Look at net result per trade, profit factor and drawdown together.

How long should I paper trade before considering a live account?

There is no fixed number of days. What matters is enough forward trades across changing conditions to compare honestly with the backtest. If the paper results drift far from the backtest, find out why before going further.

Key takeaways

A coin trending does not make a strategy better; test it as if the coin were boring.
Model fees, slippage and funding first, since thin edges often disappear there.
Small samples and many tuned variants inflate results; use out-of-sample tests and adjust for the number of attempts.
Judge drawdown before total result, and set a pause level in advance.
Forward paper testing narrows the gap with live trading but doesn't close it.

Paper trading results are simulated. Past results don't predict future results. Crypto trading can lose money, including all capital. Not financial advice.

Originally published on BOTLAB. Score your own bot's trade log free: Check your bot.