Exercise: you got to send someone money, but the payee didn't publish a bitcoin or LN address you trust. The onchain fees are high anyway for the price of a dinner.
Nostr solves this often, but let's say you just got some other social media contacts.
Solutions:
1. LNURLw
generate an LNURLwithdraw voucher and share the link or QRcode so the recepient can withdraw with most lightning wallets any time. This needs a LNURL server. Some ways to it:
- run BTCPayServer - create a Pull Payment, share the link or QRcode
- run LNbits - create a voucher with the LNURLw extension
Custodial solutions:
- https://lightsats.com - top up in the browser and create vouchers
- hope to have this streamlined in the Blink Wallet - the PoC could be extended here https://github.com/GaloyMoney/galoy-voucher
- there is of course the BTCPay / LNbits of someone else
2. Ecash
Use ecash (that will be Cashu for now) - send the token as text and when the recipient downloaded an Cashu wallet will be able to convert the token to a lightning payment or trade it within the mint for free.
- run LNbits with the Cashu extension, connect it to your eNuts or Minibits wallet
- run a mint directly with https://github.com/cashubtc/nutshell
Custodial solutions:
- download eNuts https://www.enuts.cash/ or Minibits https://www.minibits.cash/ and use the default (or some other) mint
- looking forward to the fedimint instances in the wild
Does anyone has any other practical solution working now for async payments?
I'd like to pay bitcoiners more often, but sometimes not when I can just ask for a lightning invoice.
openoms
npub14t…shy62
2024-03-24 17:20:20
Author Public Key
npub14tq8m9ggnnn2muytj9tdg0q6f26ef3snpd7ukyhvrxgq33vpnghs8shy62Published at
2024-03-24 17:20:20Event JSON
{
"id": "540f13cbbfa820a1963d033d0144057305d54b7637038f40ca2422a0c7567bc1",
"pubkey": "aac07d95089ce6adf08b9156d43c1a4ab594c6130b7dcb12ec199008c5819a2f",
"created_at": 1711300820,
"kind": 1,
"tags": [],
"content": "Exercise: you got to send someone money, but the payee didn't publish a bitcoin or LN address you trust. The onchain fees are high anyway for the price of a dinner. \nNostr solves this often, but let's say you just got some other social media contacts.\n\nSolutions:\n1. LNURLw\n generate an LNURLwithdraw voucher and share the link or QRcode so the recepient can withdraw with most lightning wallets any time. This needs a LNURL server. Some ways to it:\n- run BTCPayServer - create a Pull Payment, share the link or QRcode\n- run LNbits - create a voucher with the LNURLw extension\n\nCustodial solutions:\n- https://lightsats.com - top up in the browser and create vouchers\n- hope to have this streamlined in the Blink Wallet - the PoC could be extended here https://github.com/GaloyMoney/galoy-voucher\n- there is of course the BTCPay / LNbits of someone else\n\n2. Ecash\nUse ecash (that will be Cashu for now) - send the token as text and when the recipient downloaded an Cashu wallet will be able to convert the token to a lightning payment or trade it within the mint for free.\n\n - run LNbits with the Cashu extension, connect it to your eNuts or Minibits wallet\n- run a mint directly with https://github.com/cashubtc/nutshell\n\nCustodial solutions:\n- download eNuts https://www.enuts.cash/ or Minibits https://www.minibits.cash/ and use the default (or some other) mint\n- looking forward to the fedimint instances in the wild\n\nDoes anyone has any other practical solution working now for async payments?\nI'd like to pay bitcoiners more often, but sometimes not when I can just ask for a lightning invoice.",
"sig": "03702a3c2225b63eaf7674f371240724861d69a2d875a2e7f30bab09bb136ccd4cc5f290ff239312919d3f4ee2808bfcaebcce4a29f2c4170e474de700f89a27"
}