cygnet3 on Nostr: I think part of the reason is because the silentpayments module for libsecp256k1 is ...
I think part of the reason is because the silentpayments module for libsecp256k1 is still under development. SP benefits a lot from the efficiency that module can provide, I see some projects holding off on implementing silent payment support until it's merged.
There's also just the general chicken/egg problem of sending/receiving support. Implementing sending is a lot easier, but there is no point if there's no good wallets to receive silent payments. And doing receiving properly, especially for mobile/light clients, is still just a lot of work.
Published at
2025-02-20 10:08:25Event JSON
{
"id": "c82744e8b38c4cabeb3719934aeb1ab8a2c65284c857ccfd7b280331ebcff9da",
"pubkey": "4273280736c08fa90977f27dca91caa460f4ab18d6392a7f3e17a1aa63b5b442",
"created_at": 1740046105,
"kind": 1,
"tags": [
[
"p",
"ffca54e078fd9884a745d70eb0159c0b8a9e7d383a4906a7484b83ebf6101dd5"
],
[
"e",
"85c0ff83c584806daaec8fe637c76969de70637809ef3171d0c8e5f322ac8276",
"",
"root",
"ffca54e078fd9884a745d70eb0159c0b8a9e7d383a4906a7484b83ebf6101dd5"
]
],
"content": "I think part of the reason is because the silentpayments module for libsecp256k1 is still under development. SP benefits a lot from the efficiency that module can provide, I see some projects holding off on implementing silent payment support until it's merged.\n\nThere's also just the general chicken/egg problem of sending/receiving support. Implementing sending is a lot easier, but there is no point if there's no good wallets to receive silent payments. And doing receiving properly, especially for mobile/light clients, is still just a lot of work.",
"sig": "43c8c695d32f5844d0c8800503ccbea7a5d436ae9eb5ae506c8b6b7fff61309381a76669998fd81e1132bb4d67c02ab33e6892ea82aa40b7a89db8f1f6c0449a"
}