Constant taxable volume
The same eligible transfer volume is repeated every period. The model does not derive volume from price, holders or past trading.
0x8a5d…18b2f
Stress-test a historic burn mechanism with explicit volume assumptions while avoiding a prediction about activity, price or relaunch timing.

Runs in this browser. No wallet, account, signature or transaction.
The model calculates burn per selected period from taxable MONSTA volume, tax rate and the burn share of that tax. It divides the distance between current supply and a chosen threshold by that fixed burn amount. This is linear scenario analysis; real volume, exemptions, implementation logic and supply-changing events are not forecast. Read the MONSTA deflation-cycle guide to inspect the documented rule and its evidence boundary in more detail.
burn per period = taxable volume × tax rate × burn allocation; periods to threshold = (current supply − threshold supply) ÷ burn per periodAt 100 million MONSTA of hypothetical taxable volume per month, a 5% tax and 50% burn allocation produce 2.5 million modeled MONSTA burned per month. A 500 million supply gap would take 200 unchanged periods. Review the documented relaunch process before treating the modeled output as present contract behavior.
Taxable MONSTA volume per reader-defined period.
Tax rate multiplied by the burn allocation of that tax.
Current supply minus a selected target supply.
The cycle model is useful for sensitivity analysis because it exposes every moving part. It is unsuitable for a calendar prediction because future taxable activity and executable protocol behavior are unknown.
The same eligible transfer volume is repeated every period. The model does not derive volume from price, holders or past trading.
Every modeled transfer uses the entered tax, and the entered portion of that tax always reduces supply.
Mints, relaunch adjustments, excluded movements and other supply-changing methods are omitted.
Reaching the target number does not prove an automatic function, supported interface or claim process exists.
Exchange volume can include buys and sells, repeated routing, internal venue accounting or trades that encounter different token rules. The input here is narrower: nominal MONSTA movement that actually experiences the selected tax and burn allocation.
When no reliable taxable-volume series exists, use a range of disclosed scenarios instead of one forecast. A low, middle and high case shows how sensitive the period count is without assigning probability to any case.
A conservative taxable-volume assumption.
Shows how slowly supply changes when eligible movement is scarce.
Scenario, not forecast.
A dated, reproducible historic observation if available.
Provides a comparison anchor without assuming persistence.
Observation period and source.
A deliberate stress assumption above the reference case.
Tests the fastest linear path under the same mechanism.
Stress case, not expectation.
Record the proxy, implementation, totalSupply result, decimals and block before entering current supply.
Connect tax and burn-allocation inputs to the contract version or historic document being modeled.
Explain which transaction types count and how exemptions or unsupported routes are handled.
A threshold narrative and an executable state transition are different claims requiring different evidence.
Use the deflation guide for the historic supply design and the relaunch guide for the separate execution questions.
Answers about linear burn projection, its inputs and the evidence limits specific to this result.
No. It converts one constant-volume assumption into periods. It does not predict future transfers, exemptions, contract behavior or supported operations.
It is only the transfer amount to which the selected tax and burn allocation actually apply. Exchange-reported volume may include paths that do not map to the contract rule.
Only part of a historic total tax may have been assigned to supply reduction. Separating them prevents the full tax from being mislabeled as burned.
The tool reports that the selected threshold has been reached in arithmetic terms. It does not claim a relaunch or any other state transition occurred.
Yes. The output uses the same unnamed period as the volume input. Label that period in your notes so the result is not mistaken for months or years.
Continue from linear burn projection with the three adjacent checks most relevant to its assumptions and unresolved evidence.
Read these relationships alongside the documented assumptions for linear burn projection. Together, the MONSTA Supply Cycle Calculator relationships identify what its result measures and which evidence remains unresolved.
linear burn from a fixed taxable-volume assumption
the selected transaction tax
an executable protocol relaunch