Volume-weighted average price (VWAP) is a benchmark built from prices and volume over a chosen interval. In crypto, the reset is part of the calculation: markets trade around the clock, so a “daily” value needs a stated boundary and timezone. Change the boundary and you change which trades or bars contribute to the average. A line without its reset rule, price input and volume unit is hard to reproduce and easy to misread.
Work a bar-based example
For a candle-based approximation, one common input is typical price: (high + low + close) ÷ 3. Multiply that price by the bar’s base-asset volume, add the products, then divide by total base volume. These three fictional bars make the arithmetic visible:
| Bar | High / low / close | Typical price | Base volume | Price × volume |
|---|---|---|---|---|
| 1 | 101 / 99 / 100 | 100 | 10 | 1,000 |
| 2 | 102 / 99 / 102 | 101 | 20 | 2,020 |
| 3 | 105 / 101 / 103 | 103 | 5 | 515 |
After bar 2, the cumulative value is 3,020 ÷ 30 = 100.67. After bar 3, it is 3,535 ÷ 35 = 101.00. The typical price rose to 103 on the last bar while the cumulative average moved only from 100.67 to 101.00 because that bar had lower volume. This is a teaching calculation, not a market observation or a trading result.
Trade-level VWAP instead weights each eligible transaction by its traded quantity. A bar approximation loses the within-bar path and may differ from the trade-level figure. Check what a provider calls “volume”: it may mean base units, quote turnover, or contracts with a multiplier. Those units are not interchangeable. Missing intervals and provider normalization also change the denominator and therefore the answer. For example, two fictional fills of 1 BTC at $100 and $110 give a base-volume VWAP of ($100 + $110) ÷ 2 = $105. Weighting instead by their $100 and $110 quote turnovers gives ($100 × $100 + $110 × $110) ÷ ($100 + $110) = $105.24. That is a notional-weighted average, not the same base-volume calculation. Convert quote turnover back to base units at each price when base-quantity weighting is intended; for derivatives, also check the contract multiplier.
Check the volume field at the data boundary
The field name is part of the method. Binance’s spot kline endpoint labels base-asset volume and quote-asset volume separately: in its documented response tuple they appear at positions [5] and [7]. A BTCUSDT spot bar can therefore carry a BTC quantity series and a USDT turnover series for the same interval. Choosing the turnover field weights more heavily by higher-priced activity; it does not reproduce a BTC-quantity VWAP. That field numbering belongs to this endpoint’s schema, so do not copy it to a different venue or product.
TradingView’s chart-information reference says the volume unit varies by instrument: it is typically base currency for crypto pairs and contracts for futures and other derivatives. Confirm the chart’s reported unit as well as the API field. For a contract series, record the contract multiplier and exposure definition before converting quantities; a contract count is not automatically an amount of BTC. Save the raw field, unit, quote currency, symbol, interval, timezone, and source version beside the calculated series. Keep raw and normalized values so another reviewer can reproduce the denominator.
Declare the reset, not just the formula
For a cumulative session calculation, record the reset timestamp, timezone and daylight-saving rule. An anchored VWAP resets from a selected event or date; record how that anchor was chosen and whether it was known at the decision time. Selecting an anchor after seeing a swing high introduces hindsight into the research. In the TradingView Pine Script v6 documentation, the VWAP example accepts an explicit reset condition. That illustrates an implementation choice; it does not establish one universal session for every crypto market or charting tool.
Crypto has no single opening bell. A UTC day, a local equity session and an event anchor create different windows. If the hypothesis concerns a named local session, convert each date with a timezone database rather than applying one fixed UTC offset through daylight-saving changes. Decide the boundary before evaluating outcomes; trying many reset times and keeping the best one is another parameter search.
The signal timestamp matters too. A completed-bar VWAP based on that bar’s final high, low, close and volume is not known until the bar closes; a live indicator may move while the bar is still forming. If a rule compares the final close with that final VWAP, label the signal at the close and model an entry at a later available price. TradingView’s current strategy documentation says its default historical broker-emulator market order fills at the next bar’s open. That is a platform-specific simulation convention, not a guarantee about a real venue or this product’s engine. Filling at the signal bar’s close requires a separately justified timing model and can create an optimistic result if the decision used data that only became final at that close.
Before testing, write down the market and feed, price input, volume unit, reset boundary and timezone, treatment of missing or zero-volume bars, signal timestamp, assumed entry timing, fees and spread. Then freeze those inputs. A missing interval can distort both the cumulative numerator and denominator; a period with no eligible volume has no defined VWAP. If changing the reset after reviewing results changes a decision, log the new version and evaluate it on later untouched data.
Turn the line into a testable question
VWAP can describe execution relative to a benchmark or serve as an input to a research rule. A price crossing the line is not, by itself, a reason to trade. Write down the exact trigger, when it becomes knowable, the entry assumption, exit, invalidation and baseline. Recalculate with declared alternative reset boundaries and higher fee and spread assumptions. Keep all tested variants in the experiment log so the most attractive window is not mistaken for an untouched discovery.
SuperQuant’s bundled hourly examples are synthetic and cannot answer a venue-specific, trade-level execution question. The current research UI does not expose a general VWAP indicator builder. Use the market-session guide to declare a window, the data-quality checklist to inspect coverage, and the cost guide to challenge a small apparent edge. This is a method example, not a signal or individualized investment advice.
Download the VWAP input audit worksheet to record the field mapping, units, reset, timestamps and test variants before calculating or comparing a series.