How Fhenix Built Developer Intelligence for its FHE Builder Community with Snag
Nick Handy
·
Business Development Manager
Jun 27, 2026
·
3 min read
Fhenix brings fully homomorphic encryption to Ethereum, letting developers run confidential computation on encrypted data through its CoFHE coprocessor, live on Arbitrum. Their growth depends on builders actually using their encryption contracts, so Fhenix’s DevRel team needed to see who those builders were, what they were shipping, and which dApps were driving real encryption activity. They built that visibility on Snag.
The Challenge
Fhenix had an active, high-quality builder community, but the DevRel team was working without a clear view of it. Recognizing and supporting the right builders meant answering questions the existing tooling could not:
Who is actually running encryptions and decryptions through the TaskManager contract, and at what volume?
Which dApps are driving the most onchain encryption activity, not just signing up?
How do you connect a builder’s GitHub identity to their onchain wallet, so you can see who is really shipping?
How do you rank and reward genuine builder contribution rather than surface-level engagement?
Without that, decisions about grants, DevRel support, and fundraising introductions were being made without a system of record for who was doing the most with FHE.
What They Built
Fhenix used Snag to stand up a white-label developer intelligence layer that turns onchain encryption activity into a ranked, readable view of their builder community.
On the User Intelligence side, Snag tied each builder’s GitHub profile to their wallet, creating a single builder identity and giving the DevRel team true exposure into how builders are shipping. That identity feeds builder profiles and two levels of leaderboard: one ranking individual builders, and one ranking the dApps building on Fhenix. The team can see, at a glance, which builders and which applications are actually moving the network.
On the Programmable Incentives side, Snag configured custom onchain logic tied to Fhenix’s own contracts, tracking decryption events, encryption events, and compute operations run through the TaskManager contract. That logic drives the program’s rules, from a builder’s first decrypt and first task through escalating milestones for running 10, 100, and 1,000 tasks, plus a Weekly Active Builder rule that rewards sustained activity. Lighter social and repository actions, connecting GitHub, starring the fhenix-contracts repo, and following Fhenix, form the entry point that pulls builders into the program.
The whole system is white-label and functions as a DevRel CRM: it exemplifies usage, tracks it in real time against Fhenix’s contracts, and gives the team a back end to read it all.
The Impact
In the first two months of the program, more than 100,000 wallets ran a decrypt event through Fhenix’s TaskManager contract, and Snag tracked over 600,000 decryption events across the network. Beyond the volume, Fhenix’s DevRel team now has a system of record for their builder community: they can organize builders across hackathons, ecosystem programs, and their broader community, see which dApps are their strongest long-term contributors, and route grants, DevRel time, and fundraising introductions to the teams doing the most with their FHE infrastructure. Instead of guessing who their best builders are, they can see it.
Why Snag
Tying GitHub identity to deployer wallets, tracking custom encryption events on your own contracts, and ranking real builder contribution is hard infrastructure to build, and it is not what an FHE research and development team should be spending its time on. Snag delivered it as a white-label layer Fhenix could stand up and manage, giving DevRel the intelligence they needed without pulling engineers off the core protocol.
Building developer intelligence for your ecosystem? Talk to us at partnerships@snagsolutions.io.
Want to stay in the loop?
Subscribe to our mailing list to be the first to know about future blog articles.
