BlockchainCommons / BlockchainCommons/keytool-cli

--cosigner option?

Ouverte
#14 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
C++
Étoiles
6
Forks
5
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
cpp
Domaine
blockchain, cli, cryptography
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.