A working protocol that looked inactive

• 2 paid integrations

  requested by new clients after the campaigns and business development.

• 2 field campaigns

  an in-person hackathon and a cryptographic quest, in one ecosystem week.

• 8 BD conversations

  with privacy and infrastructure projects, two of which became partnerships.

• 2 months

  of momentum after the campaigns ended, measured against a prior baseline.

The situation

The technology worked and was mature enough for outside businesses to build on. The node operator base was large, and the community was still there, mostly quiet. Outside that circle, the website and the name made people doubt the project was alive. Inside it, nobody could say clearly what the foundation, the council and the community were each responsible for.

A protocol in that position does not have a technology problem. It has a trust problem that looks like a marketing problem, so more reach would only have spread the doubt further.

How we worked

• Interviews with early investors, technical founders, council members, developers, node operators, community members and external partners.
• Research on users, stakeholders and investors, a token and treasury analysis, and new revenue designs around the API.
• Two field tests of our assumptions during a major ecosystem week: an in-person hackathon and a cryptographic quest that ran across several venues in the host city. The baseline was measured before either started.
• Business development with eight privacy and infrastructure projects.

What we found

1. The technology was ready for external businesses. Outside engineers were excited by it and liked working with the team.
2. The story was wrong, not the product. What the protocol actually does and what people thought it did had drifted apart, and the line between its ethos and its product was blurred.
3. The trust surface made it look inactive. The website and the name worked against a protocol that was running.
4. Governance was undefined. Foundation, council and community roles were unclear inside and out, and the community expected reform.
5. There was no liquidity for business work. Without a treasury, every business activity meant selling into the market.

What we recommended

In priority order: brand and website, the product offering, the council, the sales funnel.

• Governance. A working group with stakeholders to redefine responsibilities, goals and rewards. A one-page diagram of who does what, who pays and who earns. Open council meetings at least monthly during the transition, and published annual reports.
• Treasury. A liquidity plan instead of open-market sales: weekly over-the-counter sales of a fixed fiat value covering twice the burn rate, priced on the previous week's average, over 18 months, with an upfront cushion so the treasury never has to sell into weakness. The goal was to need no such sales after 18 months.
• Business. BD and marketing funnels, a deeper push on the API use case, development and BD spend brought level, and every new application run as test, verify, close.
• Brand. A new name, an updated brand book, and a public story built on reputation rather than a pure technology overview.

What happened

• Two new clients requested paid integrations.
• Two partnerships started, one of them an API integration with a privacy compute network.
• Ecosystem work started or restarted: an iOS app, a wallet integration, and five hackathon projects carried into follow-up work.
• The token traded between 66 and 111 percent above its pre-campaign level from the campaign week until about two months after the campaigns ended, then settled above where it started. That is a correlation with the campaign window, measured against a baseline taken beforehand. It is not a forecast and not a claim about value.
• The website redesign stopped unfinished when the budget was cut.

What we would tell the next team

Working technology does not sell itself if the public cannot tell it is alive. Fix the trust surface first: the name, the site and who is responsible for what. Then test demand in the field against a baseline, so you know whether the response lasts after the spend stops.