Skip to content
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

Add support for Aleo #15

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add support for Aleo #15

wants to merge 1 commit into from

Conversation

clehner
Copy link
Member

@clehner clehner commented Nov 30, 2021

CAIP-2 proposed definition: ChainAgnostic/CAIPs#84

Implementation: spruceid/ssi#348

An Aleo account address is an Edwards BLS12 public key. This PR proposes to use BlockchainVerificationMethod2021 as the verification method type. That is a verification method type based on blockchainAccountId.

A signature/proof type, AleoSignature2021, is proposed for use with Aleo accounts using this verification method, in spruceid/ssi#360.

Copy link
Collaborator

@oed oed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. Should we wait with merging this until the CAIP PR is merged?

@clehner
Copy link
Member Author

clehner commented Nov 30, 2021

@oed Probably should wait - unless @AleoHQ prefers otherwise and/or we don't mind keeping track of unapproved CAIP-2 namespaces.

Rebased to fix conflict with #14.

@bumblefudge
Copy link
Collaborator

bumblefudge commented Dec 2, 2021

Resolved on today's calll to hold off until upstream merge at the registry, and merge as-is if that occurs as-is, rediscuss if changes needed.

@clehner
Copy link
Member Author

clehner commented Mar 24, 2022

Mentioning on call today... still waiting on CAIP approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants