[DRAFT] Keyring spec

[frankiebee]

@entropyxyz/sdk/keys

import Keyring from `@entropyxyz/sdk/keys`
import { generateMnemomnic, mnemomnicToSeed } from `@entropyxyz/sdk/keys`

const mnemomnic = generateMnemomnic()
const seed = mnemomnicToSeed(mnemomnic)
// this of course is an optional key the case here is that a user would like to also load a key they used to deploy programs
const dev = mnemomnicToSeed(mnemomnic, 'my/dev/path')
const keyMaterials = {
  programMod: seed, //or private key
  dev,
} 

const keyring = new Keyring(keyMaterials)

const keyStore = keyring.json()
/*
needs more thoughts:
{
programMod: '0x0123...' //private key? seed?
dev: '0x345...' // private key? seed?
device: '0x789...' // private key? seed?
}

const keyring2 = new Keyring(keyStore)

*/

init

should take all "3" seeds but only requires programMod i'm still stuck on this name i'd prefer not to call it it the program mod sense it's not that till we register it

are curent way of thinking is to have an admin key and registration key
the key that pays for registartion and the key that gets set as the programMod

they can be one in the same (infact they are right now)
however they can also be different. In my personal case i would want them to be different

i think also for "sponsorship" reason we should allow them to be different

Open questions:

• should you be able to set a different keyring to an already initialized entropy?

entropy.setKeyring(Keyring)