Request: when one transaction contains two legs that offset each other, pair them before any gain or loss is computed, instead of booking one leg as a disposal and leaving the other unpaired. Two patterns cover most cases: (a) a burn and a mint of identical quantity in the same transaction, such as fragSOL burned and wFragSOL minted; (b) a deposit with a receipt token received in the same transaction, such as fragSOL deposited into an Exponent vault and ELP-fragSOL received.

Why it matters: today the burn or deposit leg is priced as a total loss and the mint or receipt leg is dropped. In my account this produced about $121,000 of losses that never happened, across eight rows on two unrelated protocols (Fragmetric and Solayer), so it is not a single-protocol coverage gap. The row type MULTI_TOKEN_TRADE shows the engine already sees both legs. Example on Solana: a single transaction with 186 fragSOL out and 186 wFragSOL in; the hash and seven more of this shape have been provided to support. A generic rule, equal quantity or receipt-linked legs inside one transaction, would fix the whole class.

Who benefits: anyone using liquid staking wrappers, vaults or LP receipts gets correct results without manual edits, and these rows stop being mis-tagged as spam.