hampus
Hampus

Maker of Blixt Wallet, a non-custodial Lightning Wallet
https://blixtwallet.github.io
Funded by HRF and OpenSats.

⚡️ [email protected]

Public Key

npub1v4v57fu60zvc9d2uq23cey4fnwvxlzga9q2vta2n6xalu03rs57s0mxwu8

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsx2k20y7d83xvzk4wq9guvj25ehxr03ywjs9x974farwl78c3c20gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsqw8l8e

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1v4v57fu60zvc9d2uq23cey4fnwvxlzga9q2vta2n6xalu03rs57s0mxwu8

Show more details

Last Notes

2024-09-23 17:33:17 GMT

- reply

Hi, sorry we had a disruption on the Lightning Box server. It should work again.

2024-09-11 00:40:35 GMT

- reply

Hey, I’m easiest reachable in the Blixt chat as others have recommended (https://t.me/BlixtWallet)

2024-03-12 13:19:19 GMT

I made a Telegram bot that auto-replies to new or infrequent users.
Scammers impersonating devs and DMing users are very common in wallet chat groups. My hope is that this will prevent people from getting scammed.
The bot written in Deno and you can easily deploy it on Deno Deploy (or self-host on your own server).
https://github.com/hsjoberg/telegram-autoreplier-bot
Code is released under public domain.
The bot is currently live in our Blixt Wallet chat group.
Example scenario on how the bot works:
```
User: I need help please
Bot: Hi there user. Beware of scammers
<Nasty scammer impersonating a dev DMs the user>
User: Oh nice, thanks for the heads-up, kind bot.
```
We’ve seen that a welcome message isn't sufficient protection as people just don't read these. Even you make it crystal clear about scammers.
My rationale here for the bot is that they will notice if the bot replies directly to the user's message so they get pinged about it.
Cheers guys.

2024-03-12 13:14:20 GMT

- reply

Hi, yes as Dee Kay said, Zaps and Lightning Address (LNURL-pay) are different things.
I’m looking at fixing proper Zap support for Lightning Box though. :)

2024-02-17 12:06:02 GMT

Kotlin error looking good 😎
https://nostrcheck.me/media/public/nostrcheck.me_2816669593660138011708171543.webp

2024-01-24 11:45:24 GMT

- reply

Awesome

2024-01-20 14:52:40 GMT

- reply

Waiting for close usually indicates connectivity problems to the peer. For coop close you need to communicate with the peer.
Try manually connecting in settings -> Lightning Network -> Show Lightning Peers -> +.

2024-01-15 18:39:45 GMT

- reply

Jeremy MVP for real

2023-12-15 23:04:13 GMT

- reply

Liquid alone is just another dumb blockchain. It does not scale.
You have to deploy Lightning over Liquid.
Therefore Lightning is gonna make it.

2023-12-06 18:14:16 GMT

- reply

Fantastic work!
How big is the challenge-response onchain footprint?

2023-11-28 20:20:32 GMT

- reply

Cheers!

2023-11-28 17:22:02 GMT

- reply

Yes. But not ostriches.

2023-11-25 19:31:05 GMT

- reply

The hold invoice stuff does not really need any customization to lnd really. Last time I checked Zeus's code it was pretty close to vanilla lnd. Same as Blixt.
Also, BOLT12 is in the pipeline for lnd, so that's not true.
What other stuff are you referring to?
Lnd is first out with Taproot channel support, which is great for privacy, which Zeus and Blixt now ship with.

2023-11-25 17:23:08 GMT

- reply

Yeah, I just released Blixt Wallet v0.6.9-420 with support for receiving via Lightning Address in Android.
We take a little different approach than Zeus here. You need to run Blixt in the new “persistent mode”, which means it will always stay active in the background to receive payments (and sync the chain).
The zaps will not be held, they will just settle immediately as the app is active to receive.
Perhaps not for everyone, but I’ve been testing this for quite some time now and it’s pretty cool. So those who accept this trade-off should give it a shot.
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.9-420

2023-11-24 15:53:14 GMT

- reply

People are brainwashed by thought-leaders and podcasts telling them that Bitcoin is perfect, so it’s a waste of time trying to convince them.
Unfortunately I think things need to get waay worse fee-wise before people wake up.
Furthermore there are deep problems in the technical community too, where a small minority is pretty loud in refusing any covenant solution whatsoever, even if 10000 use-cases are presented to them.

2023-11-23 19:58:48 GMT

- reply

Nevermind it was my fault lol.
#note1gaj…ye3j

2023-11-23 19:57:29 GMT

Okay I’m dumb!
I changed my Lightning Address on my nostr profile some month ago, but that one is no longer working.
Okay should be fixed now, it’s back to ⚡️ [email protected]

2023-11-23 19:34:20 GMT

- reply

Thank you!
Are you using Amethyst? There seems to be an issue there unfortunately. They don’t accept normal “LNURL-pay” without zap support.

2023-11-23 19:25:36 GMT

- reply

Do you have any suggestions? James O’Bernie’s PR is totally ignored.

2023-11-23 19:23:51 GMT

- reply

No, this is what made Twitter so horrible, because you were only able to do insults and short gotchas.
So everyone would do that rather than write something meaningful and well thought-out. Eventually people become totally insane from all the harassment and low-quality replies. This can be observed on many prominent Twitter/X celebs.

2023-11-23 18:41:27 GMT

Blixt Wallet is back with the final release in the 0.6.x release line, v0.6.9-420. Nice!
This version has a new feature for Android, Lightning Box.
Lightning Box is a service letting you receive via a Lightning Address non-custodially to your Blixt.
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.9-420
Lightning Box works in conjunction with Persistent Mode that was released in Blixt Wallet v0.6.9.
For things to work out well, make sure battery optimization is disabled.
Battery drain is expected to be low or not noticeable if things go as expected. Reach out if you have issues.
https://user-images.githubusercontent.com/3824379/284913657-1397f859-abff-4deb-bcc0-72657f1d6ff5.webm
The Lightning Box service will forward Lightning Address (LNURL-pay) requests directly to the wallet app on the phone, so it can respond back with an invoice created by the wallet itself.
This means that while this service is not a custodian, there is still trust involved.
Lightning Box is free and open-source software and anyone can choose to run their own service provider.
https://github.com/hsjoberg/lightning-box
In Blixt Wallet settings, you can easily change the server to your own.
The Blixt Wallet project will host a Lightning Box instance for @blixtwallet.com addresses.
A draft bLIP specification for the inner workings of this protocol can be found here:
https://github.com/hsjoberg/blips/blob/lnurl-forwarding/blip-lnurlforward.md
It is built using Lightning P2P messages, so any lightning node wallet implementation can choose to implement this protocol.
That's all for now. Cheers and Happy Blixting! 🟡⚡️

2023-11-22 13:46:27 GMT

- reply

Nice

2023-11-22 11:24:46 GMT

- reply

Nice

2023-11-17 17:41:51 GMT

- reply

Indeed.
Few understand this.

2023-11-16 17:14:31 GMT

- reply

No. It’s actually in the pipeline and being worked on. I apparently know more about this than you, so maybe you should not talk about things you don’t know about.

2023-11-16 17:04:44 GMT

- reply

That’s just not true. BOLT12 is in the pipeline.

2023-11-12 14:04:56 GMT

- reply

Tackar!

2023-11-12 09:54:07 GMT

Nice. Blixt Wallet is back with v0.6.9!
We have a lot of new stuff in this release, such as a new stable Tor implementation, Persistent Mode, Simple Taproot Channels support, 0-conf channels support for Dunder LSP, and a bunch of new languages.
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.9
---
This release has a new Tor backend ("newtor") on Android that should be much more robust and reliable.
You don't need to do anything in order to experience it, just make sure you have Tor enabled in Blixt settings.
---
Blixt Wallet now has support for Simple Taproot Channels!
Your private channels will just look like normal Taproot transactions if you do a coop close, which is great for privacy.
Dunder LSP & autopilot will also support this feature in the near future.
---
Blixt Wallet on Android has a new Persistent Mode, which lets Blixt stay in the persistently in the background.
This can be helpful if you're awaiting a payment, or if you just want to keep in-sync with the chain.
Depending on the device, this mode may drain more battery life.
In a future release, we will allow self-custodial Lightning Address support for users opting in to the Persistent Mode.
---
There were a lot of more stuff than the ones discussed here, so be sure to read the changelog.
If you wish to download the app, head over to https://blixtwallet.com.
Thanks to all contributors in this release and Happy Blixting everyone! 🟡

2023-11-07 20:57:52 GMT

- reply

Yes, biggest L take I’ve ever heard.
You can still be popular and make good software in open source.

2023-11-06 13:24:19 GMT

- reply

Right. Too small amounts can unfortunately be a bit tricky at the moment.
I am trying to figure out solutions for this in the long-term so that you can onboard just some few sats.

2023-11-06 13:23:08 GMT

- reply

It’s dynamic depending on the current on-chain fee situation (+ possible subsidy by the Dunder service host, right now it’s 50% for the official Dunder server).
Fee approximation and minimum amount can be read here:
https://dunder.blixtwallet.com/ondemand-channel/service-status

2023-11-06 09:06:18 GMT

Blixt Wallet v0.6.9 is around the corner.
https://nostrcheck.me/media/public/nostrcheck.me_7362097403242307091699261498.webp

2023-10-22 09:41:19 GMT

No, Lightning is not dead.
But let this be a wake-up call that we should not put all our eggs in one basket.
We need to explore alternative scaling ideas.
Therefore I am supportive of the covenants softfork and the OP_CAT proposal, which help many Layer 2s.
https://covenants.watch

2023-10-05 08:14:36 GMT

- reply

Sure. All channels are by default private channels when you open in Blixt.

2023-10-05 08:13:17 GMT

- reply

Sorry, try again now. I have been working on other things recently so my Lightning Box ([email protected]) was not available. Should work now again as I’m back to testing Lightning Box.

2023-10-03 17:59:50 GMT

Mobile LN nodes and wallets rock!

2023-09-07 17:33:37 GMT

Testing to post to a cool new relay

2023-09-07 11:44:05 GMT

- reply

If you open a non-broadcasted 0conf channel from your own node to your own Blixt Wallet, there is no risk.
Unless you’re schizophrenic.

2023-08-26 17:49:52 GMT

- reply

Sounds like a bug. I’ll look into it

2023-08-26 17:48:36 GMT

- reply

Cheers Perlover!
Happy to hear you playing around with Blixt again.
We actually have an upcoming “persistent mode” coming to Blixt Android in the next version.
This would allow Blixt to always be online and active, like the pinning you’re talking about.
Building on top of the persistent mode, I will add Lightning Address support for Blixt via Lightning Box: https://github.com/hsjoberg/lightning-box

2023-08-08 20:45:12 GMT

- reply

What value does this provide other than break other WebLN clients?
It’s completely useless. It serves no real purpose whatsoever.

2023-08-08 20:40:58 GMT

- reply

There is no point and there is no need.
No, it’s not worth adding to the spec.

2023-08-08 20:32:24 GMT

- reply

There is absolutely no benefit to this whatsoever.
It's only needlessly breaking other less popular implementations when websites choose to follow this proprietary thing.

2023-07-07 16:44:43 GMT

- reply

Hard NACK

2023-07-02 17:02:55 GMT

Is red meat, white rice and broccoli a good diet for bodybuilding?

2023-07-01 20:58:17 GMT

3D graphics peaked with Warcraft III in 2002.
It went downhill from there.

2023-06-30 19:38:18 GMT

- reply

Awesome to hear.
Happy Blixting! 🟡

2023-06-28 13:27:43 GMT

I’m very happy to announce Blixt Wallet 0.6.8!
It contains a new feature called speedloader by @npub1xw0…y3xc, which syncs LN channel db on app startup, leading to robust payment pathfinding.
We want to thank Breez, which this work is derived from ⚡️
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.8
Speedloader loads the channel database file on app startup.
On Android, the channel database file that speedloader uses is automatically cached by a background sync job every 24h.
On iOS & macOS, the file is also downloaded on startup, leading to slightly longer startup times.
https://twitter.com/i/status/1674029478115266560
-
Blixt Wallet 0.6.8 has better support for hodl invoices.
On-going payments now show up as "pending" in the transaction log before they are eventually settled or cancelled.
This should result in a better experience when using services like RoboSats.
-
Blixt Wallet 0.6.8 introduces 0-conf channel support!
Add pubkeys for nodes you would like to accept 0-conf channels from.
https://twitter.com/i/status/1674029483525849091
-
Speedloader is open-source and can be used with a normal lnd instance.
https://github.com/djkazic/speedloader
Primer is used for generating the channel db file.
https://github.com/djkazic/primer
In a future Blixt Wallet version, we'll add the ability to choose endpoint for downloading the channel db file.
-
Blixt Wallet 0.6.8 includes a crash fix for certain iPhone devices.
Known affected devices are:
iPhone 5/5s/6/6s/7/X/XR.
If you have experienced issues in the past, please give a fresh installation of Blixt Wallet a try. 🪄
-
Happy Blixting everyone! 🟡

2023-06-21 15:32:27 GMT

People still look at the Bitcoin price?

2023-06-10 16:08:39 GMT

- reply

Yep pretty good stuff

2023-06-09 11:59:23 GMT

- reply

Sure, see here: https://github.com/lightning/bolts/pull/780
Author is René Pickhardt.
Some of the comments to this proposal is just peak insanity IMO.

2023-06-09 11:22:02 GMT

Yet another centralized service (Lightspark) being a menace to the network by doing evil probing is not fixing Lightning.
In order to promote self-custody, we need tools to improve reliability for self-custodial wallets:
- Native probing (BOLT14)
- Blinded paths
- Stuckless payments
- Async payments

2023-06-07 14:26:13 GMT

- reply

Cheers man! 🙏

2023-06-03 14:35:48 GMT

- reply

We're targeting a beta release for 0.6.9.
If you have Telegram, join our chat group @BlixtWallet, because I will talk and coordinate Lightning Address support from there.

2023-06-03 09:14:05 GMT

Blixt Wallet and Blixt Wallet Testnet have been reinstated to the Goople Play Store.
Link to Blixt Wallet:
https://play.google.com/store/apps/details?id=com.blixtwallet
Link to Blixt Wallet Testnet:
https://play.google.com/store/apps/details?id=com.blixtwallet.testnet
Happy Blixting! 🟡

2023-06-02 15:18:50 GMT

Our appeal for the suspension of Blixt Wallet and Blixt Wallet Testnet on Google Play has been accepted.
The apps are currently under review. We expect them to be back soon!
The suspension was due to app similarities, but we've clarified that Blixt Testnet is for testing only.
As always, you can download the APK directly from our releases page on GitHub:
https://github.com/hsjoberg/blixt-wallet/releases
In order to stay up-to-date with releases, we recommend you to use the tool Obtainium:
https://github.com/ImranR98/Obtainium
Read more about this in DarthCoin's article:
https://darthcoin.substack.com/p/bitcoiners-mobile-device #note1u93…k7m8

2023-05-31 18:08:30 GMT

Blixt Wallet and Blixt Wallet Testnet have been suspended from the Google Play Store.
We are working with Google on figuring out why.
In the meantime, you can download the wallet APK on GitHub.
https://github.com/hsjoberg/blixt-wallet/releases

2023-05-31 09:35:14 GMT

- reply

This is the only information I got from Google:
https://i.imgur.com/aJO6aKL.png
I have submitted an appeal. Let’s hope it’s just some algorithm error.
They also suspended Blixt Wallet Testnet, so I assume it’s because they think Blixt Wallet [Mainnet] and Blixt Wallet Testnet are the same thing, which is obviously not true.

2023-05-29 13:44:21 GMT

- reply

It’s a special rule for private channel openings.
…which people should do anyway

2023-05-29 13:43:24 GMT

- reply

It’s a new scaling tech

2023-05-25 14:51:18 GMT

My email is getting too many support inquiries for Blixt Wallet. I cannot keep up.
If you need immediate help, please join our Telegram chat group. We are a strong and helpful community.
https://t.me/BlixtWallet

2023-05-24 12:54:50 GMT

- reply

Can ask the question in small brain language instead?

2023-05-24 12:39:24 GMT

- reply

Mental illness

2023-05-23 09:51:22 GMT

Real wizards use https://ide.scriptwiz.app, not robes.

2023-05-23 09:21:01 GMT

- reply

Yes, it opens towards the Blixt project node.
https://mempool.space/lightning/node/0230a5bca558e6741460c13dd34e636da28e52afd91cf93db87ed1b0392a7466eb

2023-05-22 09:16:41 GMT

- reply

Long text good. Short text bad

2023-05-22 09:12:37 GMT

- reply

Lmao no it’s the complete opposite.
Character limitation prevents meaningful thought and expression, and people instead just resort to primal insults and nasty gotchas.
Nostr is 1000000x better than Twitter, because you can actually discuss things here.

2023-05-21 23:41:44 GMT

- reply

Fair. I actually prefer the old SIGHASH_NOINPUT over SIGHASH_ANYPREVOUT, because it’s simpler.
Anyway let’s just do both APO and CTV and call it a day. They’re both trivial.

2023-05-21 12:47:03 GMT

At this point, it's clear that many prominent scaling technologies being proposed for Bitcoin are reliant on either OP_CTV or SIGHASH_ANYPREVOUT.
Seeing how SIGHASH_ANYPREVOUT is such a simple softfork, I suggest that we start moving towards an activation for it in Bitcoin.

2023-05-10 21:55:50 GMT

There is a proposal out there to change the internal encoding format of nostr from text-based (JSON) to binary.
This is a huge mistake. One of the primary reasons why we have such vibrant ecosystem today is because of the simplicity of the nostr protocol, which means it’s easy for developers to create applications and tools.
Furthermore adding another encoding format puts a lot of burden of the whole ecosystem of services, clients, relays and tools.
Let’s don’t lose what we have. Don’t adopt NIP-88.
https://github.com/nostr-protocol/nips/pull/512#issuecomment-1542851434

2023-05-09 17:58:21 GMT

The Blixt community thanks the Human Rights Foundation for the open-source grant awarded to Hampus. ⚡️🟡
https://nostr.build/i/e0806c266fc276d68a2dcbe9ce92dc367d1ff5aa479b78e3ee9a4719f52ce7ff.jpg
#note1vza…szr4

2023-05-09 17:57:05 GMT

2023-05-06 18:04:40 GMT

- reply

Those things don’t take us that far.
But yes, I agree that we should do things like CISA, as that would make it possible to have more transactions within the current weight unit limit.
Really, it’s a shame that Taproot didn’t include CISA already.

2023-05-06 17:50:56 GMT

- reply

Additional explanation by Lightning developer René Pickhardt on this topic:
https://bitcoin.stackexchange.com/questions/87735/how-can-i-create-htlcs-below-dust-limit-satoshi-in-lightning-network/87738#87738

2023-05-06 17:25:59 GMT

Is it Lightning's time to shine now when the onchain transaction fee is so high?
Well yes, partly.
But please understand that Lightning ceases to work if the fees are too high!
To understand why, let’s go back to the saying that “Lightning is just Bitcoin transactions”.
Yes, this is true. Lightning in the end relies on normal Bitcoin transactions.
So by knowing this, you should have already realized why Lightning under a high onchain fee market is fragile, but let me explain:
The primary problem I’m referring to is the economical viability to sweep HTLCs.
An HTLC is the thing that gets added as an output to your lightning commitment transaction when you are doing Lightning payment.
It gets cleared out by making a new commitment transaction once the payment has goes through.
But the problem here is that if the onchain transaction fee is $100 and the cost of the sweeping an HTLC output is $100, then that means it’s not actually economically possible to redeem these funds.
Under normal circumstances you would never have to force-close and redeem this onchain, but it _can_ happen.
How LN circumvents this problem is by giving the payment amount to miners instead as a substitute for a real HTLC output. Giving the sats to miners means no more bytes are added to the commitment transaction, but it also means that if a force-close happens, these sats will just be given to miners instead.
This was already the case for all smaller payments (21 sats and so on) including virtually _all_ zaps here on nostr.
But for smaller micro-transactions it’s not a big deal if a payments gets lost, because no one would cry over 21 sats.
But if it’s about 210 000 sats, then we’re in a BIG problem if this isn’t secure and trustless.
We need to find a sweet spot for onchain transaction fees and we need more scaling solutions that work together with LN in order to fix this.
My favorite solution is a Lightning Network deployed over multiple Drivechains, fully interoperable, but I’m open for more suggestions. What do you think?

2023-04-13 17:25:57 GMT

- reply

Try it out for Android, iOS and macOS here: https://blixtwallet.com

2023-04-13 17:25:42 GMT

Blixt Wallet is the tinkerer's wallet.
Check out how many things you can do in the settings.
https://i.imgur.com/yl65eg2.mp4

2023-04-11 19:11:48 GMT

- reply

Well, nostr will probably work the best with fee speech too.

2023-04-10 18:53:15 GMT

- reply

https://i.imgur.com/g0MDxH5.png

2023-04-10 18:52:24 GMT

Gonna watch the Super Mario movie now LFG. ✌️
https://i.imgur.com/m9NLxkN.png

2023-04-08 08:45:17 GMT

- reply

Should work now!

2023-04-08 08:21:19 GMT

- reply

Oh! Yeah the Lightning Address is broken, just a sec

2023-04-08 08:14:41 GMT

Epic! Blixt Wallet 0.6.6 has been released, and it's better than ever before.
It includes lnd 0.16 with support for bimodal pathfinding (based on Pickhardt Payments).
Enjoy potentially speedier payment by enabling it in settings.
Happy Blixting! 🟡
```
## Common
* Updated lnd to v0.16
* Added support for bimodal pathfinding (based on Pickhardt payments). Enable it in Settings!
* Added the ability to set a label for a contact in the contact list
* Sats amount on Overview screen is now grouped
## Android
* Lowered the scheduled sync job interval from 4h to 2h
## macOS
* Fixed restoring not working properly
```
https://i.postimg.cc/HjGKhCxq/Blixt-order66.jpg
https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.6

2023-03-31 15:15:44 GMT

- reply

Yeah plans for receiving to a Lightning Address in Blixt Wallet is planned via Lightning Box.
But support for zaps is not planned. Note that you can still of course receive tips from nostr though.

2023-03-27 12:23:45 GMT

- reply

Well, one of the concerns is the one your raised on Twitter.
Few people seem to understand or know that your channel opening transactions leak in your invoice routehints.
This can be fixed either by blinded routing (BOLT11/12) or alias scid (BOLT11).
Another concern I have is the fact that seemingly no LN wallet today let’s you enforce min X number of hops.
As Lightning is an onion routed payment network, the more hops you do, the more privacy you potentially get.
Fewer hops lead to bigger risk of de-anonymising your payment.
A lot of people are using custodial LN wallets in order to have a Lightning Address, simply by the fact that it’s by far the easiest option. The only options available right now are custodial or a self-hosted routing node (which few have).
I’ve a project called Lightning Box that tries to improve things by forwarding the LNURL-pay request to the phone. Privacy-minded people can use a wallet that has Tor integrated to not leak info.
#[2]

2023-03-25 18:15:00 GMT

- reply

This is a really good summary of #Blixt! ⚡️

2023-03-24 16:11:42 GMT

- reply

Miner fees primary purpose is to support the network’s security. That’s how it has to sustain itself when block reward decreases.

2023-03-24 15:54:39 GMT

Bitcoiners who don't like ordinals & wizards need to understand that the original true meaning of Bitcoin Maximalism is that Bitcoin will cover all use-cases.
It's a good thing that we now see higher miner fees, leading to a more healthy and robust network.

2023-03-23 22:00:22 GMT

- reply

It’s also not fully trustless.

2023-03-23 21:46:02 GMT

- reply

Depends on what you mean by that.
Yes, Blixt Wallet basically has full coverage of the LNURL suite.
It does not support receiving via a Lightning Address however, which is true for all non-custodial wallets today.

2023-03-23 17:37:45 GMT

- reply

Yeah it’s in beta, but there are many people using Blixt on a daily basis.

2023-03-23 17:04:22 GMT

- reply

I agree. It’s actually not that important.
In fact it’s not important at all.
Real payments are important.

2023-03-23 07:50:39 GMT

- reply

Just forget about the federated part. It’s confusing af.
Basically it’s a service that will connect to your LN node somehow (lnd REST etc) and request an invoice.

2023-03-23 07:24:29 GMT

- reply

I am working on a zap protocol based LUD-18.
It will be very similar to NIP57, so should be easy to implement.
But it’s me against the world here, so I don’t really expect widespread support.
But I will at least try to do what I think is the right thing, instead of just complaining.

2023-03-23 07:21:19 GMT

- reply

I don’t think it matters that LUD-18 wasn’t sufficiently supported by wallets.
Nostr clients want to consume the LNURL-pay code anyway and then send the BOLT11 invoice to the LN wallet, so zaps could’ve just used LUD-18 and wallets would not have to support LUD-18.
Though hypothetically, if wallets supported LUD-18 too, both nostr clients and LN wallets could support LUD-18 zaps.
Also, I’m not blaming people having fun with zaps. I’m just very sad and frustrated at how things came to be.

2023-03-23 07:14:23 GMT

- reply

Yeah it solves it depending on how you view things. This introduces a completely new protocol. A hardfork.
So what happens if you want to use some LNURL-pay extension together with zaps, for example LUD-18 (https://github.com/lnurl/luds/blob/luds/18.md)?
You kinda can’t. All must obey NIP57, as it takes precedence.

2023-03-23 07:01:03 GMT

- reply

It’s simply not compatible.
NIP57 zap mandates that the description hash of the invoice has to be the zap request note, whereas conventional with LNURL-pay invoices, it’s the LNURL-pay metadata that should be the desc hash.
So basically a zap is not really using LNURL-pay, it’s just the same URL endpoint.
So now all LNURL-pay servers has to also support this new propertary protocol.
If we’re going to think long-term, this can have some seriously bad implications, as both LNURL-pay and NIP57 progresses and moves forward.
But I can give you a clear-cut example: LUD-18 (https://github.com/lnurl/luds/blob/luds/18.md) also let’s you commit arbitrary payer identities to a payment (which is the primary goal of NIP57).
But seeing how NIP57 takes precedence, there’s no way to use NIP57 and LUD-18 at the same time, which is just sad.
To make things in the right way, zaps should’ve just used the already specified and established way to commit data, which is LUD-18.

2023-03-23 06:26:42 GMT

- reply

I don’t like zaps.
It breaks LNURL-pay compatibility for no good reason.
It’s a very sad state of affairs.

2023-03-22 23:51:29 GMT

- reply

Should’ve been a square instead 🟩

2023-03-22 10:19:32 GMT

- reply

Hey did you hear about that wallet called Blixt?