Someone asked me recently how I am receiving #zaps since I'm using Phoenix to send them (after Alby sending broke).
The answer is still Alby, since receiving still works.
However, Phoenixd is looking like a possibility in the near future.
Just wanted to share that for anyone who cares. I've put zero work into figuring out how this will work or how practical it is at this point.
I will definitely share my thoughts once I work on implementing it.
Sovereign #zaps sounds really cool.
Matt - Strategic Bitcoin Reserve Czar
npub1l6…uj5rc
2024-04-01 11:15:23
Author Public Key
npub1l6scds4yv7xmcsmhqnhdy9sggm520q09lvts2m5mkvecgr2mmmeqsuj5rcPublished at
2024-04-01 11:15:23Event JSON
{
"id": "b484a8c7e1418db76a71fbb966f963e9af48abc1939b4967d4c70020d3e37425",
"pubkey": "fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2",
"created_at": 1711970123,
"kind": 1,
"tags": [
[
"t",
"zaps"
],
[
"t",
"zaps"
]
],
"content": "Someone asked me recently how I am receiving #zaps since I'm using Phoenix to send them (after Alby sending broke).\n\nThe answer is still Alby, since receiving still works.\n\nHowever, Phoenixd is looking like a possibility in the near future.\n\nJust wanted to share that for anyone who cares. I've put zero work into figuring out how this will work or how practical it is at this point.\n\nI will definitely share my thoughts once I work on implementing it.\n\nSovereign #zaps sounds really cool.",
"sig": "4312522b1b41befcec7332de8cf621a55a332eef9e64859864173dac443dae56e35b9f1096397ebb568248bf11f5db72e50512678d223dfdef7202dffc729ecf"
}