#CLN We're finally deprecating pay (in favor of xpay) in the next release: Greenlight has conclusively demonstrated that it's more effective across the board. That begins the 12 month window to removal.
We've long had `xpay-as-pay` for xpay to take over pay commands. Flipping that to default true and running the tests has been eye-opening.
Given our commitment to not breaking users, I'm re-learning things about pay. For example, if you try to pay the same invoice twice, pay "succeeds", whereas xpay says you've already paid. So when acting as pay, xpay needs to do that too.
Mostly, the xpay error messages are much more informative and readable. But in a couple of cases they didn't use the correct error *code* (eg. There's a specific one for "route too expensive") so that's fixed.
After this, I'll get back to my new "repeatpay" command and plug-in, which is a higher-level way to deal with recurring offers (an experimental option for now).
Rusty Russell
npub179…elz4s
2026-04-26 00:23:51 UTC
Author Public Key
npub179e9tp4yqtqx4myp35283fz64gxuzmr6n3yxnktux5pnd5t03eps0elz4sSeen on
wss://nostr.winePublished at
2026-04-26 00:23:51 UTCEvent JSON
{
"id": "9ff4a0d23a6da13f85e4481ecb7431c61b36d2bb9d929b9feeaf0d968409960b",
"pubkey": "f1725586a402c06aec818d1478a45aaa0dc16c7a9c4869d97c350336d16f8e43",
"created_at": 1777163031,
"kind": 1,
"tags": [
[
"alt",
"A short note: #CLN We're finally deprecating pay (in favor of xp..."
],
[
"t",
"CLN"
],
[
"t",
"cln"
],
[
"client",
"Amethyst"
]
],
"content": "#CLN We're finally deprecating pay (in favor of xpay) in the next release: Greenlight has conclusively demonstrated that it's more effective across the board. That begins the 12 month window to removal.\n\nWe've long had `xpay-as-pay` for xpay to take over pay commands. Flipping that to default true and running the tests has been eye-opening.\n\nGiven our commitment to not breaking users, I'm re-learning things about pay. For example, if you try to pay the same invoice twice, pay \"succeeds\", whereas xpay says you've already paid. So when acting as pay, xpay needs to do that too.\n\nMostly, the xpay error messages are much more informative and readable. But in a couple of cases they didn't use the correct error *code* (eg. There's a specific one for \"route too expensive\") so that's fixed.\n\nAfter this, I'll get back to my new \"repeatpay\" command and plug-in, which is a higher-level way to deal with recurring offers (an experimental option for now).\n",
"sig": "a79e2cbd383a088623c8d734c3ed7c0fd253d983e0842f2d6fe34f66885ecb6c380b5f9477d2f8384f0c4b4da1e8b484943ba0425c7a4f6951495be5934cbf53"
}