Skip to content

terminal-activity: the same 63.9% was on a second board, via the windows - #3030

Merged
Flotapponnier merged 1 commit into
devfrom
fix/window-take-rate-gates
Oct 17, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
fix/window-take-rate-gates

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

#3029 cleared the take-rate bench, and the headline panel and per-chain table on /compare/fomo-vs-pump-fun went away as expected. The page still showed 63.9%, twice.

The survivor is a different board: the Trading terminal leaderboard, whose Take rate / Take rate 7d / Take rate 30d columns read terminal_window_take_rate_pct, built in windows.go, which had neither gate.

pump.fun, leaderboard board, as published
  Take rate      63.9 %      ($910.86 over $1,424.96)
  Take rate 7d   11.4 %      ($7,590.99 over ~$66K)
  Take rate 30d   0.13 %     ($165.0K over ~$127M)

Same defect over three windows. The Solana leg reports nothing and is correctly excluded from the ratio, which is the existing zero-fee-day rule working. Excluding it is right. Using what is left as the platform's take rate is not.

Both gates now apply to the windows too.

  • A day whose fee exceeds 10% of its own volume never enters a window, numerator and denominator together.
  • The all-chains window needs at least half the platform's volume on measurable days. Per-chain windows are whole by construction, so the floor is not applied there and a genuinely measured chain keeps its own rate.

Both constants move to package scope. Two files share them now and a second copy would be a second thing to forget.

Volume, transactions and share are untouched: a dropped day still counts everywhere it is a measurement rather than a ratio.

Tests. Two new ones on the window path: the implausible day must not reach 1d, 7d or 30d on either the chain or the all-chains slice while a plausible platform keeps its 1% on all three, and a platform whose fees are believable but cover 0.01% of its volume gets its all-chains rate withheld while keeping the measured rate on the chain that was actually measured. Full suite green, gofmt, go build, go vet, 253 specs valid.

Copy. The leaderboard methodology described only the zero-fee-day rule and now states both gates.

Needs the VPS redeploy of ocb-terminal-activity to take effect.

#3029 cleared the take-rate bench. The compare page still showed 63.9%,
because the leaderboard board reads a different metric family:
terminal_window_take_rate_pct, summed over 1d, 7d and 30d in windows.go,
which had neither gate. pump.fun published 63.9% / 11.4% / 0.13% there.

The arithmetic is the same defect over three windows. $910.86 of Base
fees divided by $1,424.96 of Base volume, while the $40.6M Solana leg
reports nothing and is correctly excluded from the ratio. Excluding it
is right; using what remains as the platform's rate is not.

Both gates now apply to the windows as well as the daily cells:

- A day whose fee exceeds 10% of its own volume never enters a window,
  numerator or denominator. It is the source attributing a fee to the
  wrong denominator.

- The all-chains window needs at least half the platform's volume on
  measurable days. Per-chain windows are whole by construction, so the
  floor is not applied there.

Both constants move to package scope, since two files now share them and
a second copy would be a second thing to forget.

Volume, transactions and share are untouched: a dropped day still counts
everywhere it is a measurement rather than a ratio.

The methodology now states both gates on the leaderboard spec, which
previously described only the zero-fee-day rule.
@Flotapponnier
Flotapponnier merged commit 088f6aa into dev Oct 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant