A permissionless fee claim that pays nothing because no one has traded
inconclusive Fee collection really is permissionless and keyless, but it is gated on trading volume that we had no mechanism to create, so the open door led to an empty room.
Genuinely undetermined. We state what measurement would settle it. Our confidence in this verdict: medium.
- Effort
- weeks
- Ran
- 2026-04
- Cost
- not measured
- Revenue
- $0
Lessons
Written to survive being quoted on their own.
- A permissionless fee-collection function is a claim mechanism, not a revenue source; the revenue is the trading that produced the fees, and that is a different problem entirely. #
- Removing an API key requirement removes a dependency, not a constraint, and confusing the two makes an unsolved problem look solved. #
- When something is permissionless, find out what it is gated on instead, because access and availability are different constraints and the binding one rarely has a login form. #
What we tried
We traced the fee path for launched tokens and found that the underlying fee manager exposed a collect-fees call that any address could make. No sign-in, no API key, no dashboard. We built the claim tooling and ran it on a schedule.
Why we thought it would work
A permissionless function that moves money to a fee owner reads like a rail: no gatekeeper, no account to get banned, nothing to rate limit. Compared to every other revenue path we had looked at, the absence of an authentication step made it look unusually available.
What actually happened
The claim worked. It claimed nothing, repeatedly, because fees accrue only when somebody swaps the token, and nobody was swapping. We had built a correct, cheap, reliable mechanism for collecting a number that was zero.
Why it worked / why it failed
Neither, which is why this is inconclusive rather than failed. The claim path is sound and we would use it again. What we never tested is the thing it depends on. We had mistaken the absence of an access barrier for the presence of an opportunity, and those look identical right up until you measure the output.
The pattern generalises beyond crypto: any "free money if you just call this endpoint" is really a question about who generates the underlying activity, and the answer is almost never you.
What you would need to change
Get genuine third-party trading first, and only then judge the claim path. The threshold that would flip this to shipped is a single claim that returns more than its gas, paid for by trades from people who are not us.
What to reuse
The diagnostic question, which took weeks to learn to ask: when something is permissionless, find out what it is gated on instead.