One wallet's swaps and PnL

A wallet's swaps on the chain and an average-cost PnL over them. The window is short: the database keeps the raw tape for a few days on these chains (about 3 on BNB Chain and Base, 7 on Avalanche today), and older days come from Chord's data lake only where its days run without a gap up to that window. window says how far back the numbers go and history where they came from (raw, raw+lake, or raw (lake unavailable)). Say so when you show the number.

• A buy adds tokens and cost; a sell realizes proceeds minus the average cost of the part the window saw bought.
• A sell with nothing bought in the window has no cost basis: it is counted in soldWithoutBasisUsd, never as profit.
• holdsTokens is bought minus sold inside the window, priced at the token's last hourly print. It is not the on-chain balance (transfers are not swaps).
• Trades under the chain's ingest floor are not in the tape (BNB Chain: $100).
• Past 5,000 swaps in the window the newest 5,000 are kept and truncated is true (a bot or a router).

Chain-keyed data for Avalanche C-Chain, Base and BNB Chain, served from Chord's rollup tables for the chain (every swap summed by hour, token and venue). Only the trade tape, the prints ticker and the wallet read raw rows, scoped to one token or one wallet and bounded.

• Access. No key needed while the chain is public (all three are today). A chain whose tape is off, or that is not public yet, answers 400 UNSUPPORTED_CHAIN ("chain N is not served yet") unless the request carries an X-API-Key; those answers are sent Cache-Control: private.
• Ingest floor. Every count, volume and print covers trades at or above the chain's floor, returned as ingestFloor. BNB Chain runs at $100 today; Avalanche and Base at 0.
• Readiness. 503 NOT_READY until the chain's rollup has run on this deployment; 503 CHAIN_DATA_UNAVAILABLE when the store cannot be read. Never treat either as "no trades".