Avatar
Stelios
95a69326449931adda32e7e0f6275bec0e387abeee4bb56b3e94f46a6ac402e2
co-founder & cto @ geyser.fund Spreading Bitcoin is the way to adoption.

It only takes a quick glance at web dev history to understand central banks will be re-invented post hyper-bitcoinization.

Which wallet is this?

Bitcoin can be a tool for empowerment, for a fairer world. Bitcoin can also be a tool for oppression, for control.

Bitcoin has no virtue, put it to use for what you want it to be.

Replying to Avatar Sherry

Ping nostr:npub1jknfxfjynyc6mk3juls0vf6mas8rs747ae9m26e7jn6x56kyqt3quttcvj

Trying to ping Metamick but cannot find his npub πŸ˜‚πŸ˜‚πŸ˜‚

Click create project then breath should be fine

Hey nostr:npub1h50pnxqw9jg7dhr906fvy4mze2yzawf895jhnc3p7qmljdugm6gsrurqev, happy to help you out! Feel free to message me.

Replying to Avatar nothenry

Too true πŸ™ƒ

What about those parts, taken directly from the NIP:

"If the zap request is valid, the server should fetch a description hash invoice where the description is this zap request note and this note only. No additional lnurl metadata is included in the description."

"Zap receipts are only created when the invoice description (committed to the description hash) contains a zap request note."

"Parse the bolt11 description as a JSON nostr event. This SHOULD be validated based on the requirements in Appendix D, either when it is received, or before the invoice is paid."

I interpret them as referring to the description itself.

Am I understanding right that NIP57 requires the invoice description of the Zap invoice to be set to the Zap request?

Running into issues where the invoice description byte size is higher than the LND limit, so wondering if I'm reading the spec wrong. nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpremhxue69uhkvet9v3ejumn0wd68ytnzv9hxgtmsdac82mrpwgq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqrzexjn

🫑 check TG, I think it’s an issue with the node

Replying to Avatar Marce

Feeling inspired by nostr:npub1jknfxfjynyc6mk3juls0vf6mas8rs747ae9m26e7jn6x56kyqt3quttcvj and nostr:npub1h0fd5xu8rfhwdkkjr78ssdhm7rdjyf97hhjqr9acwv77ux0uvf8q23kvcg changing my nostr zap address to Bitcoin Sranan’s Fruits For Sats too! πŸŽπŸŠπŸ’πŸ“πŸ‘

https://geyser.fund/project/kindertehuistamara nostr:note1y8mc9un3strxyek0t033wfynm3vgmr0efcctc5s6xz8re3hatsaste8el0

Fruity πŸ‰πŸ‰

Time to update to a new Geyser lightning address!

From now on all zaps to my profile or notes will go to Bitcoin's Sranan's Fruits For Sats education project πŸŽπŸ‰πŸ₯­πŸ₯

https://geyser.fund/project/kindertehuistamara

nostr:npub1h0fd5xu8rfhwdkkjr78ssdhm7rdjyf97hhjqr9acwv77ux0uvf8q23kvcg are they on Nostr? πŸ‘€

Hey, what type of issue are you getting?

Is anyone else using like 5 Nostr clients?

Primal for Notifications

Damus for overall browsing

Snort for zapping with custom amounts

NostrChat for DMs