mirror of
https://github.com/luxfi/graph.git
synced 2026-09-24 00:26:07 +00:00
zeekayandHanzo Dev
74f7996ba3
A token's page showed $74,100 of volume over zero transactions, and the protocol claimed 16,062 trades above pools holding 14,827 of them. The volume had just been made a fact about the whole swap table while the count was still a tally kept as events arrived — and a tally drifts on every restart and re-index, which is the argument that made poolCount derived in the first place. Pool, token and protocol counts are folds of the same grouped read that answers for volume, so the two columns cannot disagree. The tallies are deleted rather than corrected: a second writer for a derived field is the defect, not its arithmetic. This makes txCount mean trades. Mints and burns stop counting toward it. That is a narrowing, and it is the number a reader comparing it to the volume next to it is owed. What a create handler owns is the registration itself, which is what its tests assert now. Co-authored-by: Hanzo Dev <[email protected]>