Problem

The end-to-end client tests accessing a test validator only test creation.

Solution

Test all instructions

The documentation states the program is deployed to Solana mainnet idDa4XeCjVwKcprVAo812coUQbovSZ4kDGJf2sPaBnM, but there is nothing there: https://explorer.solana.com/address/idDa4XeCjVwKcprVAo812coUQbovSZ4kDGJf2sPaBnM

Connect the client and driver update functions with the program "write" instruction

Problem

There are a lot of tests commented in program/test/functional.rs which would double check a lot of the instructions for updating and closing accounts.

Solution

Make them work

Problem

The program and client currently assume a size for DIDs of 1000 bytes, which can be wasteful for sparse DIDs.

Solution

Add a new size parameter to the Initialize which decides how many bytes to allocate on the DID account.

Problem

The on-chain program and end-to-end tests need to get tested / formatted / clippy'ed on PRs.

Solution

Add it

Instead of:

// generate an X25519 key, eg using 'tweetnacl'
import nacl from 'tweetnacl';

const keyPair = nacl.sign.keyPair();

Can we use an ED25519 keypair?

import { Keypair } from "@solana/web3.js";
const keyPair = new Keypair();

Since people are already likely to be using @solana/web3.js?

Edwards keypairs (ED25519) are better than X25519 but they're not a hundred percent interchangable - from this crypto StackExchnage answer:

Under the birational equivalence of Curve25519 and edwards25519, each X25519 public key corresponds to two possible Ed25519 public key

Hello, I cloned the repo and did an npm install and I was trying to run npm run build in sol-did/sol-did/client/packages/cli However I get the error in the title (Cannot find module '@identity.com/sol-did-client'). Thing is, it is downloaded because $ npm list @identity.com/sol-did-client sol-did@ /home/lydacious/sol-did/sol-did └─┬ @identity.com/[email protected] -> ./client/packages/cli └── @identity.com/[email protected] -> ./client/packages/core

Has anyone faced this issue? Thanks!

Repo description needs to be updates from Solid to Solana

Problem

Over time, as the program and spec evolves, the program will need to potentially handle multiple different formats for the DID document.

Solution

Forward compatibility! Add a version field at the start of SolidData, and make sure that it can't be written by the Write instruction

I am trying to test the implementation in a Vue.js Application.

**ERROR:**  Buffer is not defined at _getPDAKeyFromAuthority (sol-data.ts:19:8)

 import * as SolDiD from '@identity.com/sol-did-client';

 const didSolIdentifier = SolDiD.DidSolIdentifier.create(response.publicKey, 'devnet');
            console.log('DID Sol Identifier:', didSolIdentifier.toString());
            const service = await SolDiD.DidSolService.build(didSolIdentifier);
            const didDoc = await service.resolve(); // This line causes an error 

When I look at the file in question, it seems to be missing the import for Buffer. ?

Documentation Feedback: in http://g.identity.com/sol-did/#create

The documentation is not clear. e.g. It makes a difference between IDENTIFIER and AUTHORITY, which I asumed was a derived address from the AUTHORITY, which led me to attempt to create a didDoc off-chain to later use the clint lib to push it on-chain if the user decided it was time or when it was complete. -> https://gist.github.com/chongkan/a78803c61211ee592fec1666316191ac

Then, when I moved on, tried the above methods and the DID generated by the Client Lib is simple a concatenation of the wallet public_key.

e.g. did:sol:(network:){walletAddress}

Connect the client and driver with the Deactivate (closeAccount) program function.