Reconcile the LP Burn Before Treasury Exit

Reconcile an LP burn before a treasury exit by matching the liquidity share retired to the assets returned, then tracing every transfer into the treasury’s records. In a typical pool, liquidity providers hold tokens that represent a fraction of the pool. When those tokens go to the pair contract’s remove-liquidity function, the contract calculates the provider’s share of each reserve, transfers the assets out and reduces the LP-token supply. The pool’s balances and the treasury’s balances should tell the same story.

What does an LP burn actually do?

A liquidity removal redeems a claim; it does not simply destroy tokens. In a common constant-product pool, the contract uses the LP tokens returned and the total supply to calculate each asset due. The calculation uses the pool’s reserves at execution, so intervening swaps can change the amounts. The router may also enforce minimum amounts and a deadline. Fees earned by the pool are reflected in its reserves, while transaction costs and any separate service fees affect what the treasury ultimately retains.

“Burn” can describe two different actions. A removal call may send LP tokens to the pair contract’s burn function, which reduces supply as assets leave. Sending LP tokens to an inaccessible address instead gives up the claim without withdrawing the assets. For the wallet-side exchange mechanics, see this explanation of what a base swap exchange provides; it covers the exchange and what a trader receives. That flow is separate from reconciling a treasury’s liquidity redemption.

Which records should be matched?

Start with the transaction, not a dashboard total. Identify the pool, the treasury’s LP-token balance before the call, the amount submitted, and the transaction receipt. Then compare the pair’s reserve state and LP-token supply with the amounts transferred in the same transaction. The emitted events help identify the liquidity removal and asset transfers, but a complete check also follows any router or intermediary contract that receives assets before forwarding them.

• Confirm the LP tokens came from the treasury-controlled address and reached the expected pool contract.
• Match the liquidity-removal event and token transfer logs to the two assets leaving the pool.
• Trace any intermediate transfers, swap, fee, or unwrap step to the final treasury wallet.
• Compare final wallet balances with the transaction’s net receipts, accounting for gas paid by the sending wallet.

For a concentrated-liquidity position, the position may be represented by an NFT rather than a fungible LP token. The exit still requires tracking the position’s liquidity decrease, collected fees, and returned assets. Do not apply a simple reserve-share calculation to that position type.

How should the treasury record the exit?

Record the position removed, the assets actually received, and the transaction that connects them. Keep gross pool proceeds distinct from net treasury receipts if a swap, fee, or transfer followed the removal. Reconcile quantities first; value them using the treasury’s stated accounting method and the appropriate measurement time. That keeps a market-price change from disguising a missing token transfer.

Before authorizing the exit, check the pool address, asset order, recipient, minimum outputs, and any approvals used by the transaction. After it settles, reconcile the on-chain balances against the treasury ledger and investigate any difference before closing the position. The practical test is simple: the LP claim retired must be explainable by the assets that left the pool, and those assets must be traceable to their final destination.