LIGHTNING-ASKRENE-DISABLE-NODE(7)

📦
version 26.06.9 · 2 versions
, in nixpkgs unstable

💅 LIGHTNING-ASKRENE-DISABLE-NODE(7)

okay so bestie, this is the manual page for lightning-askrene-disable-node — yes it's a mouthful, yes it's iconic, and yes i'm gonna walk you through it 🎀

✨ NAME ✨

askrene-disable-node — the command that disables all channels to/from a node in a layer. that's it, that's the vibe 💅

🌸 SYNOPSIS 🌸

askrene-disable-node layer node

literally just two little args, we been knew 🫶

🦋 DESCRIPTION 🦋

okay so first things first: this command was added in v24.11 ⭐ (yes, we're keeping receipts).

The askrene-disable-node RPC command tells askrene to disable all channels connected to a node whenever the given layer is used. That's the whole thing. It's giving "nuke every channel touching this node, but only inside this one layer" 💀✨

Why would you even? Mainly to force the use of alternate paths 🔥. Like yeah, you could disable individual channels with askrene-create-channel or askrene-inform-channel, but bestie… that would be racy if new channels appeared 💀😭 and we do not do race conditions in this house.

The args:

  • layer (string) — the name of the layer to apply this change to. pick your layer, own your layer 👑
  • node (pubkey) — the node to disable. and here's the cute part: it does not need to exist 🙈 no cap, you can disable a node that isn't even real yet. ghost node. spectral node. main character energy.

🧚 RETURN VALUE 🧚

On success, you get an empty object back. that's it.

{}

empty. void. nothing. and honestly? slay. no clutter, no notes 💜

🔥 AUTHOR 🔥

Rusty Russell <rusty@rustcorp.com.au> is mainly responsible. legend behavior, fr fr 👑

🌈 SEE ALSO 🌈

go read these next, i'm obsessed:

⭐ RESOURCES ⭐

Main web site: https://github.com/ElementsProject/lightning — go touch grass in the repo, it's fine 🌸

💖 EXAMPLES 💖

Example 1: the whole pipeline 🎀

Request:

$ lightning-cli askrene-disable-node -k "layer"="test_layers" "node"="nodeid010101010101010101010101010101010101010101010101010101010101"
{
  "id": "example:askrene-disable-node#1",
  "method": "askrene-disable-node",
  "params": {
    "layer": "test_layers",
    "node": "nodeid010101010101010101010101010101010101010101010101010101010101"
  }
}

Response:

{}

see? empty object. told you. ate and left no crumbs 💅✨

🫶 reminder bestie: node doesn't have to exist, and that's a feature, not a bug.

that's the whole page, mwah 💋 this was Core Lightning v26.06.9, LIGHTNING-ASKRENE-DISABLE-NODE(7) — go disable some nodes, love u, bye 🦋💜

📦 where this page comes from