Hiro-Hosted Gaia Hub Decommissioning on May 31, 2025

Apps Storage (Gaia)
#1

We will decommission the Hiro-hosted Gaia Hub on May 31, 2025, to reinforce our commitment to decentralization and empower greater user autonomy.

If you’re currently using the Hiro-hosted Gaia Hub, it’s time to transition to a self-hosted Gaia instance. This change puts you in full control of your data and storage.

Need help getting started?

Check out the step-by-step guide here: How to Host Your Own Gaia.

What You Need to Do:

  • Before May 31, 2025: Migrate any data stored on the Hiro-hosted Gaia Hub to your self-hosted instance.
  • After May 31, 2025: Data on the Hiro-hosted Gaia Hub will no longer be accessible, make the switch early to avoid disruptions.

We’re here to support you through this transition. If you have any questions, connect with us on our Hiro Discord channels.

The Hiro Systems Team

1 Like
#2

I’m the creator of Brace.to and Justnote. Can you help check if our users are still using Hiro-hosted Gaia Hub?

We have our Gaia Hub on 1 Apr 2024 at hub.stacksdrive.com. Our new users use it by default, but our users who created their accounts before that don’t.

For Brace.to, a Gaia Hub bucket always contains a “links” folder. For Justnote, a Gaia Hub bucket always contains a “notes” folder.

Thank you so much. :pray:

1 Like
#3

It looks like migration is not possible, gaia source is not updated. Not empowering greater user autonomy!

1 Like
#4

IMHO, updating hubUrl at the account level is impractical as there is no public Gaia hub now. Maybe there should be both an app and account levels for the hub URL.

I also want to avoid depending on an external wallet. It doesn’t work on mobile. One account per app might suit some apps (not defi or social apps where a wallet and BNS are essential). Calling a smart contract directly to get a hub URL might be good enough for a productivity app.

Last but not least, this won’t be a focus. This is not in the roadmap. It must be a community effort!

1 Like
#5

@andresgalante I’m concerned about the impact this will have on Sigle users who are still using Gaia for their data storage. The May 31st deadline provides a very short migration window, especially considering the difficulties with the migration guide not working.

Would it be possible to:

  • Extend the decommissioning date beyond May 31, 2025, to allow more time for proper migration, or
  • Provide a data dump of our users’ content so we can at least serve a read-only version of that data if a full migration isn’t possible in time?

This would help ensure that Sigle users don’t suddenly lose access to their content and would give us the time to finish implementing a proper alternative to the current version built on Gaia.

#6

Hi Leo,

Thanks for raising this. We’ve extended the decommissioning date to June 15th.

We can also provide a data dump, similar to what we did with Blocksurvey: Identify Blockstack Users Within Gaia for Block Survey Migration · Issue #2213 · hirosystems/stacks-blockchain-api · GitHub.

Can you follow up on that issue and share how we can identify Sigle’s data so we can generate the dump?

1 Like
#7

@leopradel it’s also entirely possible to keep using gaia - the source code is there (or docker images) and it’s relatively simple to setup.
however, it is not being actively maintained outside of occasional module updates and you would have to host the service/data yourself.

#8

Decommissioning date: June 15th

Hi everyone, the decommissioning date for the Hiro-hosted Gaia Hub has been moved up to June 15, 2025. Please make sure to plan your migrations accordingly to avoid any disruptions.

As always, if you need help or have questions, feel free to reach out here or on our Discord.

Thanks!

#9

restoreWalletAccounts now just fails … was there some mitigation plan for this that I missed?

export declare function restoreWalletAccounts({ wallet, gaiaHubUrl, network, client: _client, }: {
    wallet: Wallet;
    gaiaHubUrl: string;
} & NetworkClientParam): Promise<Wallet>;
#10

The Hiro-hosted Gaia Hub was decommissioned yesterday, Monday, June 16th, the service is now fully offline.

As noted in my original post, Gaia data on the Hiro-hosted hub is no longer accessible, and migrations needed to happen ahead of time to avoid disruptions

#11

Sorry, to be clear this is a Stacks.js function that is part of the wallet sdk.

https://www.npmjs.com/package/@stacks/wallet-sdk/v/7.1.0

In the usage section, you can see two functions that require a gaia hub response in order to work:
restoreWalletAccounts and makeAuthResponse

I assume generateWallet uses a response in the background too … maybe not …

Either way, the wallet sdk functions are failing currently because there is no response. At least for me … Is there a discussion on how to mitigate this somewhere?

This is not related to migrating data.

#12

Got it, thanks for the heads up Dan, let me look at this and get back to you