Not really, failed htlcs incurred no costs.

原始 JSON

{
  "kind": 1,
  "id": "a2cdac07ff720a54d41f9bf57a10419fb7d6b8b169cd4f1abd21d62fc8f55bb7",
  "pubkey": "ca89cb11f1c75d5b6622268ff43d2288ea8b2cb5b9aa996ff9ff704fc904b78b",
  "created_at": 1785426151,
  "tags": [
    [
      "e",
      "d86edba40dfd505647e5ca778a54b961552a49582b8b792f1a55f4c29dc18956",
      "wss://ribo.eu.nostria.app/",
      "root",
      "ca89cb11f1c75d5b6622268ff43d2288ea8b2cb5b9aa996ff9ff704fc904b78b"
    ],
    [
      "e",
      "ab2d865729f0e69cedb4ac02b2d7b7739c1bac639965741313d4f98e1dc6bd09",
      "wss://nostr.mom/",
      "reply",
      "32637475ec0256fbd754571aeaa52c5454c9bd79fb7ac5b99f53b86cfcb9527a"
    ],
    [
      "p",
      "ca89cb11f1c75d5b6622268ff43d2288ea8b2cb5b9aa996ff9ff704fc904b78b",
      "wss://nostr.mom/"
    ],
    [
      "p",
      "32637475ec0256fbd754571aeaa52c5454c9bd79fb7ac5b99f53b86cfcb9527a",
      "wss://ditto.pub/relay"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "Not really, failed htlcs incurred no costs.\n\nYou can be more aggressive in deleting but then you start deleting p\u0026l data.\n\nI also turned on aggressive graph pruning. It will remove from graph already on one empty edge rather than two.\n\nThis might remove genuine paths with flaky nodes but they will pop back again when active.\n\nFor a routing node with many nodes this was a fair optimisation for me IMHO.",
  "sig": "5fef4fe11b79100d99439abc0dfe1fcf5710e85335f312c6a886fb0c26bf5f538894e36f3e9f15292f534286c99936f75fbdeff7b05165d1098a3ceec4b625e5"
}