My guess for on a ultimate Use Case for Gordian Seed Tool is that a sophisticated power user will store:
a number of single-signature "hot" wallet seed (one per currency as you really shouldn't cross)
one or more multisig cosigner seed (for anti-correlation keeping them separate per multisig account)
one or more single-sig identity seeds (FIDO, GPG, SSH, DIDs)
one or more a couple of "cold" keys where seed tool remembers some public key (root key), but the actual seed is stored offline in SSKR or on titanium, and if there is a crypto-request that needs a private key will ask to temporarily restore the either the seed, or a stored offline child private key, sign the request, then forget the key material.
Though Gordian Seed Tool will support crypto-request for a wide variety of types of key derivation and signing requests, and if network is one it may do some valitation, but it will not do directly cryptocurrency operations (only support them by other apps).
I see the crypto-requests coming initiall from QRs, Wallet Connect 1.0, and longer-term from some kind of deep-link (unclear how to verify these - I feel must more comfortable if they could be verified as coming from inside your device, and maybe not all requests are allowed), via some kind of TorGap technique as URs, and hopefully some future intersection of Wallet Connect 2.0 using UR & Tor.
shannona
commented
2 years ago
A work-in-progress:
My guess for on a ultimate Use Case for Gordian Seed Tool is that a sophisticated power user will store:
crypto-requestthat needs a private key will ask to temporarily restore the either the seed, or a stored offline child private key, sign the request, then forget the key material.Though Gordian Seed Tool will support
crypto-requestfor a wide variety of types of key derivation and signing requests, and if network is one it may do some valitation, but it will not do directly cryptocurrency operations (only support them by other apps).I see the crypto-requests coming initiall from QRs, Wallet Connect 1.0, and longer-term from some kind of deep-link (unclear how to verify these - I feel must more comfortable if they could be verified as coming from inside your device, and maybe not all requests are allowed), via some kind of TorGap technique as URs, and hopefully some future intersection of Wallet Connect 2.0 using UR & Tor.