A wallet's swaps

The wallet's swaps on the chain, newest first, each with the token and its symbol. Keyset-paged: pass nextBefore back as before for the next page; nextBefore is null on the last one.

The list covers the raw tape only: the last few days the database keeps on these chains (about 3 on BNB Chain and Base, 7 on Avalanche today). window.fromTs is where it starts. Older days are counted in the wallet route named by olderHistory, as totals per token, not as a list. Say how far back the list goes when you show it.

• wallet on a trade is the address the tape attributed it to; a swap sent through a router that the tape could not attribute is not in the list.
• Trades under the chain's ingest floor are not in the tape (BNB Chain: $100).

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".