TheGame icon indicating copy to clipboard operation
TheGame copied to clipboard

Update ceramic.metagame.wtf to Ceramic v2

Open dysbulic opened this issue 3 years ago • 2 comments

What would you like to be added?

From the Ceramic Discord:

[W]e are moving to Ceramic v2 in a few weeks and you’ll have to migrate your setup a bit.

Ceramic v2 has breaking changes that will require some effort to upgrade to from Ceramic v1.

I'm going to query and see if I can get more details on what exactly is going to break…

… Early reports are that this centers around the release of DAG-JOSE support in the Go IPFS daemon, and the subsequent switch to it from the JS-IPFS daemon currently in use.

Why is this needed?

This will be the working version of Ceramic for the mainnet. We'll have to update.

dysbulic avatar Feb 21 '22 23:02 dysbulic

@polimyl, it would be nice to have #1060 addressed before we go through this. I'm very curious to have a deeper understanding of this setup.

dysbulic avatar Feb 21 '22 23:02 dysbulic

From the Ceramic Discord:

We'll be releasing Ceramic V2.0 within the next few weeks 🥳

This is a large release that changes the way Ceramic nodes are configured and deployed. The biggest change in this release is that we are moving away from using js-ipfs (which we currently launch with our custom @ceramicnetwork/ipfs-daemon package) towards using regular off-the-shelf go-ipfs instead. We expect this to significantly improve both performance and stability of Ceramic. As part of this change, we have also updated the required Node version for running Ceramic from Node v14 to Node v16, and included a migration to using ESM modules. While the http api remains unchanged and backwards compatible, upgrading to the newest version of the ceramic-http-client will require upgrading the related glaze packages to the newest versions as well, to make sure they all support ESM modules.

Given the large and potentially disruptive nature of this release, we’re hoping to get some additional testing done before we release to mainnet and would be grateful to have your help in validating the release to help us make sure the upgrade goes smoothly when it is released to mainnet!

We'll be sharing more details soon on both testing and the migration process.

dysbulic avatar Mar 09 '22 04:03 dysbulic