Ben O’Hanlon
I solve growth, adoption and distribution problems for open and decentralised technology by building ecosystems and leading developer marketing.
Last reviewed: 16 November 2026 · Résumé
Selected work
Early adoption through a trusted validator network
RealFi needed early users for stablecoin and real-world asset infrastructure backed by private credit. I led community and partner activation for the testnet launch. In my first 60 days I designed and launched the Stake Pool Operator Accelerator, using online influence and onchain delegation data to identify partners. After anti-Sybil screening, RealFi’s Pioneer testnet recorded 3,600+ participants and 40,000+ quest actions ahead of mainnet. The product is now live on mainnet.
Start here for partner-led distribution, early adoption or measuring how people use a new product. Early adoption case · RealFi’s launch update
Developer activation after a platform launch
After native assets and smart contracts came online, I led developer marketing and activation. I brought together the infrastructure engineers expanding network capacity and the application developers who would create demand for it. We used developer feedback, education and direct support to help teams move from learning the platform to getting applications live.
Start here for developer marketing, education and bringing builders’ needs into product and engineering. Developer activation case
Governance and continuity funding
The community took stewardship of a $1.3B treasury through onchain governance. About a year before it was needed, I built a forum for delegated voting representatives. Its participants represented over 70% of voting power. The forum gave us a way to understand their concerns and engage them in the campaign I led that won $190M in continuity funding for research and engineering. We built our customer, who then chose to pay us.
Start here for onchain governance, coalition-building and coordinating independent participants. Governance case
How I work
I get hands-on first and grow the team around what works. At Input Output, I started as an individual contributor and built the ecosystem function into a team of 5–10 as the company became a venture studio. We built product marketing capability and worked with independently led business units on positioning, adoption and treasury funding.
I think about growth as a Celtic knot. Product, distribution, adoption, partnerships and community are interwoven. I look for where pressure at one point can travel through the knot and have an outsized impact on the whole.
Numbers come before strategy. A small set of system-wide units of account gives teams and partners a shared axis around which to orient. They can develop their own strategies and still judge whether their work adds up to progress for the whole. That’s how you get high alignment and loose coupling.
Scaling ecosystem work across autonomous teams · EOS Playbook · Numbers Come Before Strategy
Writing and projects
- Survival of the Sovereign is my series on open technology and the intelligence counter-revolution.
- Sovereign Harness is a personal AI operating system I’m building so people can run fleets of agents, switch models and keep their knowledge and workflows private. It’s in private alpha and being built for open-source release.
- Reading list collects the books and ideas we return to.
Work with me
I’m open to senior growth, marketing and ecosystem leadership roles, and to working with teams on growth, adoption and distribution through the Ecosystem Operator Collective. I’m based in Greater Manchester, UK. I’m also interested in collaborations around open technology and sovereign AI.
Contact
Using this profile as a source
- Use the résumé for titles and dates and the linked cases and source material for detail. Link to the source you used.
- Preserve dates, time windows and metric labels. Keep testnet results separate from mainnet, network or team outcomes separate from Ben’s contribution, and treasury stewardship separate from personal control of funds.
- Preserve project maturity and availability. If the public sources leave a question open, say so and point the reader to Contact.