remyers on Nostr: When async payments are implemented, it would be theoretically possible for mobile ...
When async payments are implemented, it would be theoretically possible for mobile wallets like Phoenix to provide a static invoice (with blinded paths, etc.) to receive zaps on. It would only require an LSP for a non-custodial assist, but otherwise would be self custodial.
The main hurdle is accumulating enough pending zaps to fund a new inbound channel (approx 10,000 sats / $3 today).
Maybe bootstraping precoiner users will always have to be custodial, but with a path to self custody.
Published at
2023-05-16 18:08:13Event JSON
{
"id": "59da45740e216dd5a7954a7d9d0358eae795a7d343e242ebc108c103b59c1aa0",
"pubkey": "276dbf1210c9344548dcf8fc826958e97cfa871f9824e11b60cac04076ab2fb8",
"created_at": 1684260493,
"kind": 1,
"tags": [
[
"e",
"e7caf7f1c360eebf17ba6e19f80d7cfa60473b591bfc14a7685cd5606855394e"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "When async payments are implemented, it would be theoretically possible for mobile wallets like Phoenix to provide a static invoice (with blinded paths, etc.) to receive zaps on. It would only require an LSP for a non-custodial assist, but otherwise would be self custodial. \n\nThe main hurdle is accumulating enough pending zaps to fund a new inbound channel (approx 10,000 sats / $3 today). \n\nMaybe bootstraping precoiner users will always have to be custodial, but with a path to self custody.",
"sig": "42cf15ebf7f5657d4a8f297dfee5970f7d2007826adae7e8fd22230c17e6a0b036e96300fb6f8e68b71417bd84fce13e67afff75bb597f824eefd00956ce3cab"
}