BlockchainCommons / BlockchainCommons/keytool-cli
--cosigner option?
- Lingua principale
- C++
- Stelle
- 6
- Fork
- 5
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Related to #12 & #13 & to LetheKit:
I think one of the most common uses for us (Blockchain Commons) is to get the 48h/0h/0h/2h cosigner derivation into the short text & a UR QR form (with the optional label and birthday), suitable for offering or receiving as part of a Policy Map -> Account Map process. Thus could maybe be a --cosigner shortcut option for keytool.
Currently I don't think we can use `crypto-account` for this, so we need to puzzle that through.
Note that this does not solve the problem of cosigner reuse: later we figure out a good way to have different cosigners for different Account Maps we'll need to puzzle that through as well. But a simple `--cosigner` option will help a lot.
Related, we may want to explicitly add this 48h/0h/0h/2h cosigner UR to LetheKit, as it long-term may be the most common export option from an offline seed.
/cc @gorazdko @wolfmcnally @Fonta1n3
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reviewing the keytool CLI entry points and the related issues #12 and #13, then compare the proposed 48h/0h/0h/2h cosigner flow with crypto-account and LetheKit. Done means the requirements for a --cosigner shortcut and its short-text and UR QR output are settled, including the optional label and birthday.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- Ambito
- blockchain, cli, cryptography
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100