← @ChristopherA Twitter archive

Christopher Allen

@ChristopherA

@meshcollider @pwuille Other scenarios are an encrypted signed key or xpub, or a slip39 shard with sharded metadata (say lightning info).

4/15/2020, 11:01:08 PM

Favs: 0

Retweets: 0

Christopher Allen

@ChristopherA

@meshcollider @pwuille I'd like to be able to encode this base64 2 of 3 descriptor: wsh(multi(2,03a0434d9e47f3c86235477c7b1ae6ae5d3442d49b1943c2b752a68e2a47e247c7,03774ae7f858a9411e5ef4246b70c65aac5649980be5c17891bbec17895da008cb,03d01115d548e7561b15c38f004d734633687cf4419620095bc5b0f47070afe85a))

4/15/2020, 11:03:45 PM

Favs: 0

Retweets: 0

Christopher Allen

@ChristopherA

@meshcollider @pwuille So the queston that @pwuille asked is “how many errors you want to correct”. <3% errors is considered acceptable in typing but gross errors is >6%, so 4-8 for that scenario.

4/15/2020, 11:16:56 PM

Favs: 0

Retweets: 0

Christopher Allen

@ChristopherA

@meshcollider @pwuille I wish I knew what the historical expected error rate was for ham radio operators doing voice or morse code. 10%? If true that would be 13 errors. That is my worst case % — say for terrible censorship resistance scenario.

4/15/2020, 11:18:31 PM

Favs: 0

Retweets: 0

Christopher Allen

@ChristopherA

@meshcollider @pwuille I do believe anything beyond this point SMS size (140 characters) is infeasible for these type of communications. The reality is that I'm most interested are ECDH (with its embede pubkey) at ~75 bytes, the new Schorr signatures + pubkey at ~64 bytes, xpubs & xprv unencrypted.

4/15/2020, 11:28:02 PM

Favs: 0

Retweets: 0