Imagine being a grown up man and caring about zaps

Where did you get this idea that privacy is a fundamental human right?

like share renostr if you want signing ux to be improved

BIP322Share

UX complexity of BIP322 When implementing BIP322 for SBW I’ve encountered two UX issues: Once a message is signed we have 3 or 4 different ...

Bitcoin is not that complicated, there's nothing to study for years and years. Make your mind about it and move on, life is too short to be excited about one thing only.

bip322verifybc1qhg4gdhdjnajdwx6fu0ar2gqp99lq68pt5u4z2m|379c38ada2841c1e849b20db83d3b78f279fafd12ed22efc5aa6b3593238f92b|AkcwRAIgDqSfiI4kyY/Pn2HN8rPx0zmg9XTLMdT5seAFH7wheBcCIAbIhIhc4C/xc4ADfF4Zaon6fitsMcYZHxYHht/iFi+PASEC57cx26Q/Hmlc/sqA9SQy6Ic7zl3mlmzBRMcSHXxz/x8=|RnVya2FuIHJhcnRlZA==

v2.5.5 is out. Now you can use built-in search to look for addresses belonging to your wallet and then use a found address to sign any message. Signing and verification is implemented according to BIP322 and is compatible with other wallets who also implement it (I've reused low level BIP322 code from Sparrow wallet, thanks to them for saving me some time). On top of BIP322 I've come up with a "BIP322Share" format to make all signing and verification parts portable and easy to use on mobile devices. Link to BIP322Share description can be found here: https://github.com/akumaigorodski/wallet/blob/master/app/BIP322Share.md, other wallets are welcome to implement it to make signing and verification more accessible.

BIP322 outlines how to sign and verify a message, but what about formatting a result such that it can be presented as QR for example, is there any standard for that? For example, to verify I need to get an address, a signature and a message, so 3 strings. Is there is a format to pack those into something QR-readable/copy-pastable?

2.5.4 is out. The single most important innovation here is that now you can send transactions from multiple attached wallets at once, to save on fees and easily consolidate your utxos. For example, in a video below sender has two wallets: a default one which comes with an app and a second one which was attached later (by providing another mnemonic). Sender then utilizes both of these wallets to send a single transaction into receiver wallet (receiver by the way only has a hardware wallet and no signing wallets at all, that's another new feature). Sender then realizes his mistake and cancels a transaction using RBF, both wallets react to this appropriately.

I've deactivated my twitter account and only have this now. It will get deleted in a month and then probably can be created again, but it won't be me so don't listen to it if it starts posting anything.

SBW is the lowest time preference on the market

v2.5.2 is out. Now you can attach external wallets by providing their BIP39 recovery phrases. Here's a screenshot which shows an example where a single SBW app contains 4 types of wallets including an attached one.