Not too good news if true. I did try to use LN again a bit about 7 months ago, experience was so bad as if nothing has changed since early days (payment failures), that's when I've decided it's time to call it a day.

I mean too high, damn it lol

My time preference is too low to endure another 5 years of the same thing

Questionable vendor lock, worsened UX because of higher fees (which is a consequence of non-custodial nature).

Other than this, just check download counts of Phoenix against, say, WoS on app stores.

A better question might be: is there really that much demand for Bitcoin payments? If yes, why not make it a custodial protocol to start with to remove all the complexities of a truly decentralized system?

The reasons I ask is because:

1) payments is a highly competitive industry with very low margins, LN will be constantly fighting all the world's banks and payment systems (and musk soon), and it's going to be an uphill battle for LN because it's a decentralized system and fiat solutions are actually reliable and pretty neat UX wise.

2) Non-custodial low-value payments do not have quite the same ring as non-custodial storage of large amounts of value, I fail to see why any kind of censorship resistance is even needed in majority of LN payments.

I consider LN a done deal. The reasons were briefly posted on twitter already but since twitter account is deleted I'll provide them again here.

1) Serious LN dev is hard and time consuming, I no longer have time or resources to keep it up or even maintain what has been developed so far. In my opinion the whole LN protocol is overly complex and is getting worse and at this point can only be developed by very few high profile specialists at a very slow pace. Philosophically, I think Bitcoin as a protocol should have a complexity barrier such that it does not get beyond a point where laymen just can't understand and trust it, I think LN has already passed that barrier.

2) It's been 6+ years of struggle to get LN anywhere beyond a community of mostly ideological users with no visible success or perspective. My opinion is ultimately LN is not what market at large wants from Bitcoin and folks should look into other directions besides dumb payments, and not overly fixate on LN.

3) Remaining LN demand has been mostly absorbed by various custodial solutions. A truly non-custodial LN wallet will always be worse than a custodial one in UX terms and historically we see that majority of remaining users consistently choose convenience over control. This makes developing end-user non-custodial LN solutions feel like the most thankless thing in the world.

nostr:note1c0ynwvu4urfx7qmxen4z5y6ddqp4u5hkhwt6je5cgf6s7heax7fqe9zysr

No, LN support has been dropped.

OBW is discontinued, there's only SBW now. If you ask me, NBD should have contacted me and take over SBW instead of creating all of this mess.

I think it's fair to say there's nothing natural about rights, it's all a fiction which only exists if can be enforced.

UHDR does contain the word "privacy" in article 12 and also seems to be defining the concept of fundamental human rights. Is this the document that many here refer to when they talk about these things? Because UHDR is not legally binding, it's a list of desires about how things should be from UN which can't enforce any of this.

Also while we're at it, what "fundamental human right" even is and which school of thought does it come from?

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

Yes, I now have some time to maintain and develop SBW a bit. OBW is dead as far as I know.

like share renostr if you want signing ux to be improved

https://sbw.app/posts/bip322share/

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==

https://nostrcheck.me/media/public/nostrcheck.me_8837462297133428611697282267.webp

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.

https://nostrcheck.me/media/public/nostrcheck.me_8421530198099808421697280549.webp https://nostrcheck.me/media/public/nostrcheck.me_9814233833184602851697280554.webp https://nostrcheck.me/media/public/nostrcheck.me_1353414030956169841697280560.webp https://nostrcheck.me/media/public/nostrcheck.me_2616478667827607741697280563.webp

Nice, I'll follow this, then. Is the format outlined anywhere or in code only?

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.

https://www.youtube.com/watch?v=egxYvgI4pto

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.