algorandfoundation / did-algo

The "algo" DID Method specification and tools.
BSD 3-Clause "New" or "Revised" License
18 stars 7 forks source link

UPDATES ON DID-ALGO for ALGO Projects #94

Closed kcelestinomaria closed 1 year ago

kcelestinomaria commented 1 year ago

Came across this piece of work and had a couple of questions as I lead a project on Algorand where we need an identity system(https://jasiriprotocol.org), we are still on testnet and having a robust identity system is part of our needs at the moment:

**

  1. What are the explicit goals of this DID system?
  2. Is it scheduled for public production release anytime soon or in the future?
  3. There is some work out there done on the same e.g Ceramic Network, Vendible(on Algorand) etc, already in mass use. How unique is this implementation and how is it customized for Algorand dAPPs and wallets if any? **

Looking forward to your response. Thanks!

@bcessa @fabrice102 @shaih @johnalanwoods

pbennett commented 1 year ago

NFDs (https://app.nf.domains) are used across all of Algorand already (66 integrations atm and supported in all wallets), are live on betanet, testnet, and mainnet, and provide as robust an identity solution as you'll find. Support for multi-party linking, flexible ownership models, large (soon, near unlimited) arbitrary chain-accessible metadata storage, full forward and reverse on/off-chain lookups, global API, multiple off-chain verification attestations stored on-chain (email,twitter,telegram,discord,...).
If desired, things like Vendible IDs for eg could just be metadata in the NFD, w/ NFDs being the discovery mechanism.

kcelestinomaria commented 1 year ago

The APIs enable one to enable in-app/in-wallet minting, right? 

Thanks, Celestino(e) Kariuki,

---- On Wed, 15 Mar 2023 19:21:08 +0300 Patrick Bennett @.***> wrote ---

NFDs (https://app.nf.domains) are used across all of Algorand already (66 integrations atm and supported in all wallets), are live on betanet, testnet, and mainnet, and provide as robust an identity solution as you'll find. Support for multi-party linking, flexible ownership models, large (soon, near unlimited) arbitrary chain-accessible metadata storage, full forward and reverse on/off-chain lookups, global API, multiple off-chain verification attestations stored on-chain (email,twitter,telegram,discord,...). If desired, things like Vendible IDs for eg could just be metadata in the NFD, w/ NFDs being the discovery mechanism. — Reply to this email directly, https://github.com/algorandfoundation/did-algo/issues/94#issuecomment-1470344539, or https://github.com/notifications/unsubscribe-auth/ALFYQOXBDJE2CCNXQHPU46DW4HT7JANCNFSM6AAAAAAV3VIEMY. You are receiving this because you authored the thread.

pbennett commented 1 year ago

Of course - it's an initial two-step mint / claim process, but the API is extremely simple to use. https://api-docs.nf.domains/ Feel free to reach out in the #nfd-api channel on the NFD discord if you want info on minting, etc. but the openapi docs are linked from the docs as well where you can generate clients in about 15 languages.

bcessa commented 1 year ago

Hi @kcelestinomaria, let me provide a bit more context to your questions.

  1. What are the explicit goals of this DID system?
  1. Is it scheduled for public production release anytime soon or in the future?

Is already in production and ready to use; you can:

  1. There is some work out there done on the same e.g Ceramic Network, Vendible(on Algorand) etc, already in mass use. How unique is this implementation and how is it customized for Algorand dAPPs and wallets if any?
    • The did-algo tools in this repo can be used with any wallet that supports the "wallet connect" protocol; for example the official Pera Wallet.

Finally yes, there are several other projects in the space, but as always, is very important to look closely at the details and decide what is the best solution based on your specific requirements. For example:

I hope this is helpful, best regards.

Screenshot 2023-03-15 at 17 03 21
bcessa commented 1 year ago

I'll close this ticket since there's no actionable item related to it.