HYPOTHETICAL MODEL

Test the mechanics before you trust an estimate.

Adjust a sample trade size and see how a simplified pool model changes. No wallet, quote service, or transaction is involved.

LOCAL SIMULATION · NO TRANSACTIONS
AL·01
01
02
03
POOL DEPTHRESERVES
TRANSACTIONDEMO ONLY
HYPOTHETICAL MODEL
THE CONTEXT

The Sell Impact Simulator is an educational tool for seeing how pool reserves influence a hypothetical swap. It uses a simplified constant-product model and example reserves chosen for the demonstration. It does not fetch market prices, account for every exchange fee or route, or submit transactions. The output is not a quote.

01 / PRICE IMPACTA trade changes the reserves it uses02 / SLIPPAGEExecution conditions add uncertainty03 / POOL RESERVESDepth should be read alongside trade size
HYPOTHETICAL MODELNo wallet · no live pool · no transaction
CONSTANT-PRODUCT EXAMPLE

Change the trade size. See the pool respond.

A simplified reserve model for learning, not an execution quote.

BNB
0 BNB500 BNB
Illustrative reserves500 BNB + 500K tokens
MODEL OUTPUT · NOT A QUOTE
7.41%

Estimated price impact under a basic constant-product model.

Modeled token output37,037.04
Initial reserve ratio1,000 token / BNB
Average modeled ratio925.93 token / BNB

This demonstration omits fees, route selection, gas, token mechanics, market movement, and transaction ordering. Reserves are invented examples. Do not use this output to trade.

01 / PRICE IMPACT

A trade changes the reserves it uses

In a basic constant-product pool, the product of the two token reserves remains approximately constant, excluding fees and implementation details. When a trader removes one asset and adds another, the reserve ratio changes and so does the pool’s implied price. The size of that change depends on the trade relative to available depth.

This is why a headline price does not tell you what a larger order would receive. A small pool may show a stable last trade and still be sensitive to the next order. The simulator makes this relationship visible by changing only the hypothetical input amount.

02 / SLIPPAGE

Execution conditions add uncertainty

Slippage describes a difference between an expected execution and the realized result. Price impact is one contributor, but transaction ordering, competing swaps, route selection, fees, and block timing also matter. A model that knows only two reserves cannot predict those conditions.

A production quote would need a specific chain, token pair, route, fee tier, and recent state. Even then, it could change before a transaction is included. This local simulator intentionally avoids presenting a dollar estimate or calling its result a guaranteed execution price.

03 / POOL RESERVES

Depth should be read alongside trade size

The initial reserves in this demo are round illustrative values. They are not a claim about any live token or pool. Increasing the hypothetical sell amount should produce a larger modeled price impact because a greater fraction of one reserve is exchanged.

Real pools may use concentrated liquidity, dynamic fees, multi-hop routes, or token transfer rules that violate the assumptions in this model. For pool context, visit Liquidity Radar, where the factors that should accompany a real reserve snapshot are explained.

04 / SCENARIOS

Compare conditions instead of predicting markets

Try the same hypothetical order against a shallow and a deeper reserve set. The difference illustrates why execution costs depend on the venue and not just on the token’s displayed spot price. A sudden liquidity removal can change the response to a later trade even when its nominal size stays constant.

These scenarios are educational; they do not represent historical or current BNB Chain pools. To understand how activity might appear in a monitoring workflow, see Dump Detector and Dashboard.

05 / SAFE INTERACTION

No wallet connection and no transaction path

The page has no transaction signing code. A visitor should not need to connect a wallet or approve token permissions to use a calculator. Avoid entering seed phrases or private keys into any website; a legitimate monitoring tool does not need them.

If wallet connectivity is introduced for a separate feature, it should request only the minimum permissions and explain the exact action before asking for a signature. Read Security & Transparency for the project’s current status and design principles.

06 / LIMITATIONS

Use the output to learn, not to trade

The model omits exchange fees, gas, routing, price movement between observation and execution, and token-specific behavior. Its reserves are hard-coded demonstration assumptions. A real swap estimate should be sourced from a trusted route and refreshed immediately before execution.

The simulator never executes real transactions. It is not financial advice and does not recommend buying or selling. Review Documentation for other product guides and the Risk Disclosure for important context.

QUICK ANSWERS

Good questions deserve clear answers.

These notes reflect the current prototype status. For product details, follow the linked guides and their stated limits.

Does this execute a trade?

No. All calculations are local, hypothetical, and read-only. There is no wallet connection or transaction submission.

Are the reserves current?

No. They are illustrative inputs for an educational example and are not fetched from a live pool.

Is the output a quote?

No. It excludes important execution factors and should not be used as a transaction quote.

sinkers.online

THE INTELLIGENCE BEHIND EVERY MARKET SIGNAL.

Stay ahead by staying curious. Verify the event, question the interpretation, and keep the limits in view.

Explore the dashboard