Reserves double proportionally
Impact fallsThe initial price stays similar while the same trade becomes smaller relative to depth.
MONSTA LIQUIDITY IMPACT CALCULATOR.
Model a MONSTA-to-WBNB constant-product trade from explicit reserves without presenting the result as a live executable quote.
AMM impact model
Runs in this browser. No wallet, account, signature or transaction.
How AMM impact model works
The calculator applies a selected token tax and pool fee to the nominal MONSTA input, then uses the constant-product reserve formula to estimate WBNB output. It reports average execution price and reserve-driven price impact separately. Every reserve is entered manually, so the result is a reproducible scenario rather than a live quote. Read the MONSTA liquidity guide to inspect the documented rule and its evidence boundary in more detail.
AMM impact model equation
net input = MONSTA sold × (1 − token tax) × (1 − pool fee); WBNB out = WBNB reserve × net input ÷ (MONSTA reserve + net input)AMM impact model example
Selling 1,000,000 MONSTA into a modeled pool with 400,000,000 MONSTA and 1.1 WBNB produces a small WBNB output whose average price is below the initial reserve ratio. Raising trade size increases reserve-driven impact nonlinearly. Review fee-on-transfer execution risk before treating the modeled output as present contract behavior.
Constant-product sell path
Stage 1 - Token
The selected transfer tax reduces nominal MONSTA before pool pricing.
Stage 2 - Pool
The pool fee reduces the input used by the reserve equation.
Stage 3 - Reserves
Trade size changes the reserve ratio and average execution price.
ONE TRADE.
THREE DIFFERENT COSTS.
A fee-on-transfer token sale cannot be explained with one “slippage” number. This model keeps the token deduction, automated-market-maker fee and reserve-driven impact separate so each assumption remains visible.
StageInputOperationResearch meaning
Nominal transfer
MONSTA the user proposes to sell.
input × (1 − tax)Estimates what reaches the pair under the selected token-tax assumption.
Pricing input
Post-tax MONSTA delivered to the pair.
delivered × (1 − pool fee)The amount used in the constant-product output numerator.
Reserve output
Fee-adjusted input plus starting reserves.
y × dx ÷ (x + dx)Models WBNB removed while preserving the reserve invariant.
Execution comparison
Average output per pricing input.
1 − average ÷ initial spotIsolates reserve-driven impact from the entered token tax.
Reserve order is an evidence question
A pair exposes two reserves, but their order only becomes meaningful after checking token0 and token1. Entering WBNB in the MONSTA field reverses the price and makes every downstream output meaningless. Preserve the pair address, observation block, token addresses and raw reserve integers before adjusting for decimals.
Reserve timestamps matter too. A mathematically correct calculation from an old reserve state is still an old scenario. It should be labeled with the observation time and never presented as a current executable price.
TURN THE MODEL INTO
A REPRODUCIBLE SCENARIO.
Record enough context for another researcher to rebuild the result without trusting the interface.
- 01
Identify the exact pair
Verify the pair contract, token order and decimals. A ticker or interface label cannot establish which assets the reserves represent.
- 02
Bind reserves to one block
Record reserve0, reserve1 and the observation block. Do not combine one current reserve with another value copied from an older report.
- 03
Justify both fee assumptions
Source the pool fee from the specific venue and the token tax from the implementation applicable to the modeled path. Defaults are starting hypotheses.
- 04
Stress-test trade size
Compare several nominal inputs. Constant-product impact grows nonlinearly, so scaling a small-trade rate linearly understates a larger trade.
Trade size doubles
Impact more than doublesThe reserve curve is nonlinear; average execution deteriorates as more WBNB leaves.
Token tax rises
Less reaches pricingThe pool-only impact can fall even while the seller’s total effective outcome worsens.
Continue with execution evidence
Use the liquidity guide to inspect reserve depth and the fee-on-transfer guide to understand why router support matters.
MONSTA LIQUIDITY IMPACT CALCULATOR FAQ.
Answers about amm impact model, its inputs and the evidence limits specific to this result.
01Is this a live MONSTA swap quote?
No. It is a constant-product scenario using the reserves and fees entered by the reader. Live execution can differ because reserves, routing, taxes, gas and ordering change.
02Why are token tax and pool fee separate?
They describe different deductions. The token contract may reduce the amount reaching the pair, while the automated market maker applies its own fee inside the swap calculation.
03Which reserve order should I use?
Enter the MONSTA quantity as the MONSTA reserve and the paired wrapped BNB quantity as the WBNB reserve. Confirm token0 and token1 on the pair contract before copying values.
04What does price impact measure here?
It compares the modeled average pool execution price with the initial reserve ratio after isolating the entered token tax. It is not the total difference from an external market price.
05Can the result be used as minimum received?
No. A transaction minimum needs a fresh executable quote plus a deliberate tolerance. This page never creates transaction parameters or recommends a slippage setting.
NEXT CHECKS FOR
AMM IMPACT MODEL.
Continue from amm impact model with the three adjacent checks most relevant to its assumptions and unresolved evidence.
What the MONSTA Liquidity Impact Calculator proves - And what it cannot
Read these relationships alongside the documented assumptions for amm impact model. Together, the MONSTA Liquidity Impact Calculator relationships identify what its result measures and which evidence remains unresolved.
The MONSTA liquidity impact calculator
modelsa constant-product MONSTA-to-WBNB reserve change
Token tax and pool fee
reducedifferent stages of the modeled input
A manual reserve scenario
does not equala live executable swap quote