This is just another braindump of ideas, comments and questions from scoping out next stages of development:
sam init <mnemonic> should be just a wallet like signature instead of revealing mnemonic
New keys should be hard derive ?
If Kilt user, then we should use their SS58 address, else create new one
SamOS finds a match for this DID + public key
sam rotate allows you to update the keys that manages access to a samaritan.
adding credentials simply
supply an endpoint for verification and attestation using Kilt
links to Kilt: verification and cross check with the Kilt blockchain. Kilt is used to store the trusted data about attesters and DIDs, while SamOS just provides a clean interface for Kilt users
Do you want to connect your Kilt DID - Y/N?
Retrieval of credential IDs to be appended to the Samaritan root
Is there a way to verify attestations on Kilt without big overhead?
Where would documents live (e.g. drivers license, self-authored book) and how would Kilt interact with them? User choices?
This is just another braindump of ideas, comments and questions from scoping out next stages of development:
sam init <mnemonic>should be just a wallet like signature instead of revealing mnemonicsam rotateallows you to update the keys that manages access to a samaritan.