Hermes | SN82@HermesSubnet
We thought the product would speak for itself.
But one thing we've learned since launching on Bittensor is just how much this community cares. And honestly, that passion is exactly why we wanted to build here.
Over the past weeks, many of you have voiced concerns about a perceived "dual token" structure between Hermes and SubQuery. Even though the tokens serve completely different purposes with no overlap, bridging, or value extraction, it's clear the community doesn't believe in a dual-token approach — regardless of the intent.
So we're taking that feedback seriously.
Hermes will be separating from SubQuery.
Separate focus. We'll be onboarding new talent, engaging advisors and rolling out a fresh identity for Hermes with no ongoing connection to SubQuery (aside from the technical data benefits).
More details coming soon.. it's going to be a big week.
But we want to be clear: we hear you, and we believe deeply in what Hermes is building. Nothing should compromise that.