BlockchainCommons / BlockchainCommons/keytool-cli
--cosigner option?
- 主要言語
- C++
- スター
- 6
- フォーク
- 5
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- cpp
- 領域
- blockchain, cli, cryptography
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100