BIP322Share

UX complexity of BIP322

When implementing BIP322 for SBW I’ve encountered two UX issues:

  1. Once a message is signed we have 3 or 4 different pieces of data: signature, message hash, signing address, optionally a plaintext message itself. It is hard for a mobile user to share them all at once, ideally those should be packed into a single string.

  2. When asked to sign a message with a specific address it might be cumbersome to find that address in a wallet and then copy/paste an exact message.

Portable sharing format

To solve those issues I’ve come up with a BIP322Share format to make all signing and verification parts portable and easy to use on mobile devices first (but this will make desktop user life easier as well).

Other wallets are invited to follow suit and make message signing process a more straight forward experience.