Table of contents
- SMA makes the calculation easy to inspect
- EMA emphasizes the latest price change
- VWMA changes the line through volume weighting
- Crossovers describe a change that has already happened
- Test the crossover with costs and unchanged rules
- Connect confirmed alerts to a Cornix demo bot
Moving averages in crypto trading help you read trend direction and define repeatable crossover rules. Start with SMA for equal price weighting, EMA for greater emphasis on recent prices, or VWMA when volume should influence the average. Treat their signals as reactions to past activity, never forecasts (moving average guide).
Cornix TradingView Bots execute configured trades from connected TradingView alerts, with entry, stop-loss, and take-profit settings. This provides a route from a moving-average condition to automated execution once you have defined and tested the rule (TradingView Bot overview).
SMA makes the calculation easy to inspect
A simple moving average adds the selected prices and divides by the number of observations. Each observation has equal weight. With Close selected as the source, a 20-period SMA uses 20 candle closes, not necessarily 20 days. Length, source, and chart interval therefore belong in every written strategy (SMA settings guide).
Use SMA when you want an easily audited baseline. For an educational test, choose Close as the source, length 20, and offset 0. Keep those choices unchanged while reviewing the sample. Changing the source or shifting the plotted line changes what you are inspecting; neither adjustment establishes a better trading rule.
An average smooths the path of price, but a smoother line can conceal how far the latest close has moved. Compare the current price with the underlying candles before treating proximity to an average as an entry reason.
EMA emphasizes the latest price change
An exponential moving average gives recent prices greater influence. The standard multiplier is 2 ÷ (length + 1), and the update is previous EMA + multiplier × (latest close − previous EMA). Older observations retain progressively smaller influence rather than disappearing at a fixed boundary (EMA calculation guide).
For a 20-period EMA, the multiplier is 2 ÷ 21, approximately 9.52%. That weighting makes EMA more responsive to recent changes than an equal-length SMA. Choose it when your rule deliberately needs that responsiveness, rather than because the line appears to catch a past turning point more neatly.
Keep the average type consistent when comparing tests. A 20/50 EMA crossover and a 20/50 SMA crossover are different rules even though their lengths match. Record the type alongside the lengths so your chart review and alert configuration use the same calculation.
VWMA changes the line through volume weighting
A volume-weighted moving average multiplies each selected price by its corresponding volume, adds those products, and divides by total volume over the window. A high-volume candle therefore influences the result more than a low-volume candle. VWMA answers a different question from SMA: where does the average sit when activity determines the weighting (VWMA calculation guide)?
Compare a 20-period VWMA with a 20-period SMA using the same symbol, interval, and price source. Their separation shows the effect of volume weighting within that sample. It is not an independent promise that price will follow the VWMA. Keep the chart's data source fixed so you do not confuse a feed change with a strategy change.
Crossovers describe a change that has already happened
A bullish crossover occurs when a shorter average rises above a longer one; a bearish crossover reverses that relationship. The familiar golden cross and death cross often refer to the 50-day and 200-day averages. Both combine lagging calculations, so neither establishes that a rally or bear market must follow.
The useful distinction is between a crossover event and an ongoing condition. “Crosses above” identifies the transition; “is above” remains true afterward. Write which one your strategy uses. Otherwise, a rule intended to enter once can become a rule that keeps requesting entries while the averages remain aligned.
For an illustrative long-only test, specify a four-hour chart, Close source, 20-period EMA, and 50-period EMA. Enter only after a completed candle confirms the upward cross. Define the exit separately, such as a downward cross, and state whether an existing position blocks another entry. These are test inputs, not recommended settings for every crypto market.
Review repeated reversals as carefully as sustained trends. The practical cost of a rule that changes direction frequently is more transactions, so include trading costs rather than judging it from the chart's successful crossings alone (strategy testing documentation).
Test the crossover with costs and unchanged rules
Convert the idea into a complete specification before measuring results: symbol, interval, average type, lengths, entry event, exit event, allocation, and position limit. Use a separate historical period to evaluate the chosen settings without retuning them. Optimizing and judging a rule on the same sample can produce overfitting.
Inspect drawdown, trade count, and the sequence of losses as well as net return. Add commission and a reasoned slippage assumption in the strategy properties. TradingView's broker emulator simulates fills; its results are not records of orders executed on your exchange.
For hands-on practice with entries and exits, open our TradingView paper trading guide. For the distinction between an executable rule and its exchange instructions, use our algorithmic trading guide. Keep a dated record of each test so later settings changes do not silently rewrite the strategy you originally evaluated.
Connect confirmed alerts to a Cornix demo bot
For indicator-based alerts that support it, choose Once per bar close when your rule requires a completed candle. TradingView distinguishes this from Once per bar, which can trigger while the candle is still developing. Match the alert timing to the timing used in your test (alert frequency guide).
Cornix Demo Accounts include TradingView bots with simulated funds and require the designated demo webhook when connecting alerts. Activate Demo Trading, create the demo account, configure the bot, and connect the alert using the demo instructions. Inspect the symbol, amount, entries, exits, and resulting trade together (demo account guide).
Cornix supports exchange connections by market type, including Coinbase and Kraken spot connections. Before live activation, match your exact exchange domain and account market to the supported connection; chart availability alone does not establish execution compatibility (supported exchange guide).
Keep one written crossover rule through chart review, historical testing, and demo execution. When you are ready to rehearse the alert-to-bot connection, open the Cornix registration page.
Frequently Asked Questions
Does adding more moving averages provide independent confirmation?
Not necessarily. Several price-based averages reuse the same underlying observations with different weights or lengths. Treat agreement as a description of that price history, rather than several independent forecasts.
Can a bar-close alert arrive after the candle's scheduled close?
Yes. TradingView may wait for the first trade of the next bar to establish that the previous bar has closed. Rare or delayed trades can postpone the alert, so a confirmed-close rule does not imply instant delivery (bar-close delay guide).
Can I connect an exchange testnet to Cornix Demo Accounts?
Cornix Demo Accounts use a built-in simulation without exchange API keys. Cornix does not support connecting external exchange demo accounts or testnets through API keys; create the simulated account inside Cornix instead.
