In mid-2026, Mintlayer became the first project to run a full CommunityOS scan in production. This is the story of the numbers that came back, what they meant, and the agency cascade that opened from a single deliverable.
Mintlayer is a Bitcoin sidechain for tokenized real-world assets. The team came to CommunityOS with a specific frustration: they had thousands of X followers built up across years of project activity, and no way to distinguish the real community from the airdrop farmers and dormant accounts. Every campaign started by trying to figure out who to talk to. Every campaign ended without a defensible report.
The scope of the first scan was deliberately bounded. One workspace, one full audience scan, the Act Now queue surfaced, no automation, no rewards configured yet. The deliverable was the scan itself plus the methodology walkthrough. The goal was to see whether the engine produced something the team would actually use — not whether it produced a marketing artifact.
The full audience scan produced the following bucket distribution after Bot-Kill filtering:
Total real community after Bot-Kill: 5,806. The raw follower count going in was substantially higher; the difference is the Bot-Kill filter at work.
Some people landed in two or three archetypes simultaneously. The Champions list overlapped substantially with the Builders list — typical for a technical Web3 audience.
The Act Now queue surfaced people the Mintlayer team did not know existed. A developer who had quietly shipped a derivative tool, a writer who had referenced the project in three substantive threads, a holder who had defended the protocol in a contested thread without being asked. None of them had ever been on a KOL list. None of them had ever been paid. All of them were already in the audience.
This is the pattern CommunityOS is built to find. The answer is already following you. The Mintlayer scan confirmed it in numbers.
Mintlayer’s marketing agency reviewed the deliverable. The introduction pipeline to that agency’s other clients opened on the strength of one report.
This is the agency cascade the CommunityOS go-to-market motion is built on. The first client does not just buy the product. The first client unlocks the channel.
Two more pilot slots are open before August 4. Includes the full scan, the methodology walk, and the published case study after the 60-day mark.
Apply to be a design partner