Mintlayer: 78,181 followers in, 5,806 real community out.
The first production scan ran on Mintlayer's X audience. Bot-Kill filtered nine of every ten accounts before any scoring happened. The remaining 5,806 were ranked across Champion, Amplifier, Builder, and Early Adopter — and 298 of them deserved attention this week.
Every figure on this page comes from one scan run.
Dataset ID c200ea0f-ca75-40ad-b250-37d6c1d321a8. Workspace 00000000-0000-4000-8000-000000000001. No synthesis, no compositing.
5,806 real community members. Five action buckets.
Every scored account lands in one of five buckets. The buckets are what operators act on; they aren't analytics.
Highest-priority Champions and Amplifiers. The operator's queue for this week.
Strong signal, lower urgency. Activate when capacity allows; nothing time-sensitive.
Signal present but not yet ripe. Re-score on the next scan; do not act yet.
Active community members. Track but do not pull into a campaign unless context changes.
Below the scoring floor. Real accounts, but not relevant to the brand's current motion.
71,110 accounts filtered before scoring.
Web3 follower lists carry a high percentage of farms, shells, and engagement bots. Bot-Kill removed them at the door.
The filtration rate is not a target — it is the observed rate on this specific audience. Established brand accounts tend to score lower bot percentages. The point is not the number; the point is that the queue the operator sees never includes any of these 71,110 accounts.
Three takeaways the operator runs on.
The real audience is roughly 7 percent of the headline number.
78,181 followers shrinks to 5,806 ranked accounts after the filter. That is what the brand actually has. Reporting built on the 78K number is fiction. Reporting built on 5,806 is defensible.
The decision queue is 298, not 5,806.
5,806 ranked accounts is the universe; 298 is what an operator can actually act on this week. The Act Now queue is the working surface; everything else is context.
The proof layer is the report.
When campaigns run on the Act Now queue, Proof Review verifies each completed mission before it counts. The ROI Report that goes to stakeholders is built on the verified layer, not the requested layer.
Want your scan in the next case study?
Pilot Program slots include the scan, the queue, the report, and naming credit when the case study publishes.