Solo is Moving to the Hiero Namespace

By Michiel Mulders

We’re continuing the transition of Hedera-related projects to Hiero, and today we’re announcing that Solo is officially joining that journey.

As part of the broader ecosystem migration announced in 2024, projects are transitioning from the hashgraph namespace to vendor-neutral hiero-ledger namespaces under the Linux Foundation Decentralized Trust. This transition reinforces our commitment to open source, transparency, and community-driven governance.

What’s Changing?

The Solo codebase has already been migrated to the hiero-ledger GitHub organization. However, there is one remaining step in this transition:

• The NPM package is currently still published as @hashgraph/solo
• It will be moved to @hiero-ledger/solo

Dual Publishing Timeline

To ensure a smooth transition for developers, we will use a dual publishing strategy:

• Dual publishing period: February 25th → end of July (6 months)
• During this time, Solo will be published under both namespaces:
• @hashgraph/solo
• @hiero-ledger/solo
• After the dual publishing window, the package will be published exclusively under @hiero-ledger/solo

The exact version that marks the cutover (when releases stop under @hashgraph/solo) will be communicated closer to the transition date, once it’s clear which release will serve as the final dual-published version.

What Should Developers Do?

In short: update the namespace to avoid any issues.

• Start migrating your dependency to @hiero-ledger/solo during the dual publishing period.
• Avoid waiting until the final cutover to prevent disruptions.
• Future updates and fixes will only be available under the new namespace after the transition is complete.

Solo is Moving to the Hiero Namespace was originally published in Hedera Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.