oed
commented
2 years ago Hi @rsoury thanks for starting work on Arweave support!
There are a few things to note:
- Arweave support needs to be added to CAIP-10, in CASA namespaces
- 3ID Connect auth flows are about to be sunset, in favor of DID PKH and CACAO auth
- The main method that will be relevant going forward in AuthProviders is requestCapability
- We are working on making it easy to generalize SIWE to "Sign-in with X" in the CASA working groups
- There are a few other steps needed to complete an integration, which are not completely defined yet.
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
rsoury
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&authSecretmethod for Arweave-based DID authentication.