Conversation
|
thanks for contributing! For support in did-session, the following guide explains all the details https://did.js.org/docs/guides/add-chain-support/ This pr would add support in 3idconnect, which we are not longer accepting new chains right now, and is considered legacy support, sorry for the confusion (realizing now that the legacy guide was still in docs, going to remove) Good news is the CAIP specs are an important part, and looks like those are open already, additionally a lot of what is here already will make it easy to add support in js-did/did-session, let us know if you need anything else |
|
@zachferland thanks for the info and clarifying about 3idconnect. This was part of the initiative around adding it as a draft. Don't be sorry, this is all part of the origins grant program, I'm happy to be able to dig in and help. I will start working and add it to the linked repo. |
Description
This PR is to add SUI wallet support. Sui is a new layer 1 blockchain developed by Mysten Labs, it is in the early stages of launching and is part of the Move ecosystem that originated from the development work around Diem created at Meta
The PR adds SUI support to two of the packages - blockchain-utils-linking and blockchain-utils-validation. The motivation for this PR was while trying to develop an application integrating Ceramic and Sui(specifically creating a DID) there was no support to use a Sui wallet address when creating a DID session using the
did-sessionpackage.It is being added here as a draft in case the team wants to provide context or comments. Some unit testing is done but it is awaiting local development testing using Sui wallets and guidance around the addition of CAIP's for Sui network(see below)
How Has This Been Tested?
Local unit testing
Describe the tests that you ran to verify your changes. Provide instructions for reproduction.
PR checklist
Before submitting this PR, please make sure:
References:
Please list relevant documentation (e.g. tech specs, articles, related work etc.) relevant to this change, and note if the documentation has been updated.