Now this is a good flow. Much better than the IA walled gardens of tester year.

Would this need changes to the nostr relays or would you just need to have clients that supports the protocol?

Nostr is just a messaging delivery mechanism after all.

nostr:npub1fl0cktytkd80798jzh7deumdlky3yzj88fdsexfuray2uqjj79rs63mwl4 you need to add a way to search by location.

There are too many events to look through manually.

nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx

I've been thinking on howtoo solve the dust limit problem nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze is facing. The simplest and most practical approach would be to follow the coinjoin model of having multiple pools for different size miners. Based simply on the hash rate the miner is bringing to the table, they would be placed in a pool that ensures their rewards are above the dust limit based on pools hash rate limit.

Ex. You run 3 pools, A, B, C, with 100, 10, 1EH limits respectively. Then you can filter an individual miner to the pool where their hash rate falls between 0.1% to 5% of the pools hash rate limit. Or something along those lines.

No accounts, no KYC. Just filtering based on hash rate only.

nostr:npub19kv88vjm7tw6v9qksn2y6h4hdt6e79nh3zjcud36k9n3lmlwsleqwte2qd people need to take this self-sovreignthings more seriously. Instead of immediately running to nostr and complaining, they should first see if they can solelve the problem themselves.

24hr HTLC lock times are not an attack on #lightning, at most they are simply taking advantage of your own lax routing policy. If you don't like it then simply change your routing policy. It's as simple as than.

Overall good improvements.