-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAIP10 support for Arweave Wallets #2175
Comments
Hi @rsoury thanks for starting work on Arweave support! There are a few things to note:
As you can see we are in the middle of a transition period with our auth approach. I would advise waiting for a few weeks at which point it will be easier to contribute support for a new chain. If you really need support in the current format then using a fork would be advisable! cc @3avi @haardikk21 |
Is there any documentation regarding DID PKH and CACAO auth, so that we can develop on technology that is going to be maintained? |
There will be more documentation coming. For now there is: |
Arweave compatibility with CAIP10
This is a low priority enhancement that should eventually be applied to the Ceramic Libraries.
I've created an Auth Provider here: https://gist.github.com/rsoury/72e0a79210ea156b2110fd3c19b2bb58
The intent is for compatibility with https://github.com/ceramicnetwork/js-ceramic/tree/develop/packages/blockchain-utils-linking
While desiring and attempting to develop the support, I soon realised that https://github.com/ceramicnetwork/js-ceramic/blob/develop/packages/blockchain-utils-validation is a dependency for the Core Ceramic Node meaning that integration would require a fork of the entire node.
Correct me if I'm wrong on the above statement.
I'm unsure at the moment if running a forked Node is advised.
In the meantime, I'll use
authId
&authSecret
method for Arweave-based DID authentication.The text was updated successfully, but these errors were encountered: