Noblocks removed from coverage pending revalidation

63

Apps on one relayer

the key we had treated as Noblocks

13

Venues in coverage

restated across all history

$10.96M

Week of Jul 20–26, restated

published at the time as $10.6M

We are temporarily removing Noblocks from AfriFlux coverage while we revalidate its attribution.

We found the problem while mapping the Paycrest Gateway. The Gateway records which app each order belongs to. When we checked those records against the wallets we had attributed to Noblocks, we found 63 different apps using the same relayer.

Our original attribution identified Noblocks users through that relayer key. That was wrong. The relayer belongs to shared wallet infrastructure, not to Noblocks.

The pipeline was not the issue. The wallet attribution was.

What this changes in the numbers

Rather than publish another number on a basis we cannot defend, we have withdrawn Noblocks from coverage entirely and restated the full history on the remaining 13 venues.

Restating moves prior weeks in both directions, which is worth explaining rather than leaving as a discrepancy:

• The week of 20–26 July now reads $10.96M, against the $10.6M published at the time.
• The prior peak, the week of 29 June, restates from $9.2M to $8.81M.

Removing a venue pulls a total down. Improving attribution on the venues that remain pushes it up. In late June the first effect dominated; in late July the second did. Both figures are correct on their own basis — they are simply not the same basis, which is exactly why the change is documented here rather than applied quietly.

What happens next

Noblocks will be added back once the attribution is revalidated properly, with the updated methodology published alongside it.

Previous Noblocks posts stay up, and now link to this correction. We would rather leave a wrong number visible with an explanation attached than delete it and hope nobody noticed.

The methodology page documents the change.

Attributed, not estimated. This one wasn't.