Do not treat burn as live data yet
Do not build production analytics that assume burn events are currently emitted, and do not collapse burn into removeLiquidity in your own parser.
Burn is listed as a separate pool event. It is not the same as removeLiquidity. This page shows the planned schema until real public burn messages appear.
{
"schemaVersion": "burn_event_v1",
"signature": "string",
"mint": "string",
"txType": "burn",
"pool": "string",
"poolId": "string",
"price": 0,
"source": "parsed_tx",
"slot": 0,
"block": 0,
"poolProgramId": "string",
"instructionName": "string",
"hasError": false,
"timestamp": 0,
"txSigner": "string",
"lpMint": null,
"lpAmount": null,
"baseVault": "string",
"quoteVault": "string",
"baseMint": "string",
"quoteMint": "string",
"baseAmount": 0,
"quoteAmount": 0,
"tokensInPool": 0,
"solInPool": 0,
"burnScope": "unknown"
}
Do not build production analytics that assume burn events are currently emitted, and do not collapse burn into removeLiquidity in your own parser.
Burn is already listed in the docs and backend rules, so this page shows the intended schema now while staying clear that a real public burn message is still missing.