The only free public relay i can vouch for the safety of spam is probably nostr.mom . Been using it for a while, almost no spam 😅
If you like Firefox, Fennec is also decent choice. You can check on F-Droid
I can relate, sometimes Vitor gives multiple times update in a day 😅
Well, its like dopamine hits so different 😅
Yup, only need NIP-57 and voila ready for action 😂
Oh zappr bot is back, thank you zappr and bro semisol 🙏
Btw, this is proper way to reply notes with a lot of tagged users, right? 😄
I did some digging (when I should have been working on my fiat job). Here are my findings:
TLDR: it shouldn't work for nodes with only private channels since ligess is not passing the parameter `private` to `lnd`'s `AddInvoice` RPC method:
Here are the relevant code parts:
1 - `ligess` calls una's `createInvoice`
https://github.com/Dolu89/ligess/blob/d8c71626a403a5d40f6f88b134506d7776a34d3a/router.js#L47-L53
2 - una translates and passes these parameters:
3 - una calls the `lnd`'s `AddInvoice` using REST
4 - That method has these docs (check the field `private`)
https://lightning.engineering/api-docs/api/lnd/lightning/add-invoice
5 - On `lnd`'s code base, that field has no explicit default and since it's in rust, the defaults to false
In order to fix this, one would need to patch botch ligess and una to pass the `private=true` parameter.
It seems most LN address server didn't explicitly set private route hints or have configuration for that.
I found that https://github.com/bumi/lnme has config for that. I already use it for my private LN address outside of nostr. But, i haven't decent skill in Go to patch it to make NIP-57 compatible 😅
I did some digging (when I should have been working on my fiat job). Here are my findings:
TLDR: it shouldn't work for nodes with only private channels since ligess is not passing the parameter `private` to `lnd`'s `AddInvoice` RPC method:
Here are the relevant code parts:
1 - `ligess` calls una's `createInvoice`
https://github.com/Dolu89/ligess/blob/d8c71626a403a5d40f6f88b134506d7776a34d3a/router.js#L47-L53
2 - una translates and passes these parameters:
3 - una calls the `lnd`'s `AddInvoice` using REST
4 - That method has these docs (check the field `private`)
https://lightning.engineering/api-docs/api/lnd/lightning/add-invoice
5 - On `lnd`'s code base, that field has no explicit default and since it's in rust, the defaults to false
In order to fix this, one would need to patch botch ligess and una to pass the `private=true` parameter.
Thank you #[1] , for your precious time investigation 🙏
#[0]
Is there no shower girl anymore? Someone will probably missed her 😅
Just want to drop this one as complementary, maybe can be useful:
Other Non KYC Exchange or LN supported Exchange:
- https://github.com/cointastical/Exchanges-With-LN
- https://cointastical.github.io/KYC-Free-Instant-Exchanges/
Nice, right? No KYC, Instant Exchange, support lightning. :)
Other Non KYC Exchange or LN supported Exchange:
- https://github.com/cointastical/Exchanges-With-LN
- https://cointastical.github.io/KYC-Free-Instant-Exchanges/
Hello, I don't understand Hindi, but i can understand this one thanks to Amethyst :)
The most important things is to move it to your own wallet as soon as you buy.
You need to go to your profile, edit profile > edit "LN Address" field with your LN Address like this:
youraccount@yourwallet.domain
{"content":"Running https://github.com/Dolu89/ligess/pull/9\nCan fellow nostriches help me out and test if I can receive zaps NONCUSTODIALLY?","created_at":1677156929,"id":"f0526316916936ff8be9a27e6e684b6ce486a410e58f145f9e4953b331ecb6d8","kind":1,"pubkey":"d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c","sig":"8930ffa1c603563eb8b7c41594f2d44c91f240815b89b3e257813c28653d4dd01c33dcd602e8b13bafaa5062d081bae25ee0645d9bfafcc2a14c4d8422ce7f9d","tags":[]}
If you want to try, #[7] successfully running his own LNURL server for zapps using PR from #[8] :)
#[3]
🙏 Cc #[3] #[4]
Last time i heard they give whitelist to ln.tips , WOS, and other popular custodial services
Yes, using ZEUS we can define route hints whengenerating the invoice. Need to check LIGESS code more where to define route hints properly.
Nice, hopefully it works nicely
Thanks. Hey you return it too much 😄
Btw, do you know this will work for node using private channel behind tor? I know in your case, you have public channel behind tor