pythcoiner

>The label field usage is not clear for me. Can it be removed or is it part of a communication standard ? If i understand correctly `descriptor_alias` would be equivalent...

> `keys_aliases` seems to be a good improvement for descriptor readability but we need to be careful as device cannot trust laptop and user **must** verify external xpubs. Yes, that's...

> * **for descriptor registration**, If I understand correctly your proposal: User will first see the template of the descriptor with the keys_aliases and then verify the dict of `alias`:`key`...

> * **for signing process**, user just want change outputs to be labelled with the descriptor alias, do we need to display the descriptor content or is it just a...

> Note that the serialization (and therefore the `policy_id`) also commits to the _name_ of the policy that is shown to the user when they register, not just the descriptor;...

> HMAC is a lot faster than signing, and it's recommended in this case − no advantage in asymmetric cryptography since the hardware device is both signer and verifier. I...

I start working on a rust implementation of an encoder/decoder for QRCode data [here](https://github.com/pythcoiner/BitcoinQrDecoder) (only specter format for now, the next step will be to handle UR format), maybe I...

Here are some notes about UR encoding: Trying export PSBT from sparrow I got 5 UR encoded chunks: ``` UR:CRYPTO-PSBT/1-5/LPADAHCFADIDCYCHJSBZZEHDFLHKADHEJOJKIDJYZMADAEGMAOAEAEAEADFYDRDLMUFNGLDWMHFZUYDACFTKEYEODLPFFMROLRREFZAXDKRDCTZTJOIAJTMTWDADAEAEAEAEZCZMZMZMADDICTADAEAEAEAEAECMAEBBYTLKMDMUDTSN ``` ``` UR:CRYPTO-PSBT/2-5/LPAOAHCFADIDCYCHJSBZZEHDFLJSAXRTNDENJNMUJZNSFEHTMDYLWMCAJLDEFWAEAEAEAEGWADAAECLTTKAXETPSWMRFLAAEAEAXEECEKNGLRHFRHLWMMOEEUEHLFGIEYAKNSGFRKNMYSWASMOIYFLGOGRMWTBWYKTZOAOBZGRBTFZFR ``` ``` UR:CRYPTO-PSBT/3-5/LPAXAHCFADIDCYCHJSBZZEHDFLUEBELAGLBBEMKBNYWFATVTLRAHUEWPWNTPBEHSWFNBKBMTADLYUTBDVEYKJTIHBEONSWRLJTGHAEAELAADAEAELAAXAEAELAAEADADCTPFDIADAEAEAEAEAECMAEBBIDZOCLIOLGROJODKOECWROSN ``` ``` UR:CRYPTO-PSBT/4-5/LPAAAHCFADIDCYCHJSBZZEHDFLKOROHPRDOETNPSDIKTWDCESAADAXAAADAEAEAECPAMAOVEOEWKSSMDUEBGMTAOPFUYUTHERECABZDATYKPIDLOHHPKCMKGJNLFETVYYLTDKGCSONSWRLJTGHAEAELAADAEAELAAXAEAELAVWDRVTVY ```...

> For standardization of proof of registrations, I'm not convinced a symmetric HMAC is the best choice. Some advantages of actual, asymmetric signatures: i think the PoR do not have...

btw i'm interested to have @bigspider thought about this BIP proposal