Skip to content

Latest commit

 

History

History
109 lines (57 loc) · 5 KB

README.md

File metadata and controls

109 lines (57 loc) · 5 KB
Raw

did-solana

What it's all about

Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies.

more info

Decentralized identifiers can be composed in every way imaginable and they will be "first-class citizens" of every chain in the next few years. Features such as vanity names for users, multi-user ownership, on-chain role-based abstractions, login challenges to web interfaces, group message encryption and many many more are unlocked through the use of decentralized identifiers.

Why DIDs are being used in this project

DID allow users to identify and licence AMMs and Bridges, this allows users of AMMs to have some certainty that the pool is created by a respectable authority and their funds will be safe. Bridge licences can allow a bridge program that is stored on-chain to identify themselves.

How this helps Solana

Regulation is coming to crypto, DIDs and services (such as the license-service used in this project) can allow AMMs and service providers to adhere to the coming regulation by identifying and licencing different service providers in their eco-system.

What's in this repo

identifier program

The identifier program contains the core logic to create decentralized identifiers on the Solana chain

license-service program

The license service program provides a way to attach arbitrary licences to a DID

frontend

The frontend is a basic UI that allows users to create DIDs, compose licences and public keys into their DIDs

Deployment information

For developers to build run the programs

Please refer to the project-specific READMEs

Happy paths through the application

Creating a DID and issuing your own licence

  1. Go to the Create Identifiers tab and create an identifier (this will store your key in local storage)

  2. Add an public key to your account on the Add Authentication tab

  3. Create a service to attach to your identifier on the Create Services tab, select Generic Service, remember to save the data key

  4. Add a service to your DID on the Add Services tab

  5. Query your DID on the Home tab (Hint: if you hover your mouse over the person Icon, your address will show up)

  6. Congrats your now the proud owner of a DID 🎉

Creating a DID and issuing a licence to the Serum DEX

  1. Go to the Create Identifiers tab and create an identifier called Serum Dex (this will store your key in local storage)

  2. Add an public key to your account on the Add Authentication tab

  3. Create a service to attach to your identifier on the Create Services tab,

3a. Select the AMM licence in the service type input field,

3b. The subject of the licence should be the Serum DEX program address 9MVDeYQnJmN2Dt7H44Z8cob4bET2ysdNu2uFJcatDJno

3c. Remember to save the data key for use in the Add Services tab

  1. Add a service to the Serum Dex DID on the Add Services tab

  2. Query the Serum Dex DID on the Home tab (Hint: if you hover your mouse over the person Icon, your address will show up)

  3. Congrats you made a DEX on Solana more secure 🎉

Next steps concerning this project

  • Testing of the programs

Due to time constraints tests were completely omitted from the programs

  • Improvement of the core program functionality

Again due to time constraints, some features that would improve the core functionality of the DID programs were omitted. e.g different types of keys to be allowed in the DID Document

  • Messaging feature

Allow the web-UI to encrypt data from every public key associated with a DID

  • Login to the web UI and user-controlled public keys to DID documents

Issuer a login to a user to decrypt data and allow a user to broadcast their transactions

What is not coming next

  • Web wallet interactions

Web wallets such as Metamask although innovative technology cement users into the web2.0 world by building abstractions around HTML parsers and native js environments, we need a new way to allow a user to interact with chains that don't involve browser extensions or custodial wallet.