Event JSON
{
"id": "25458e9a62b172ddd768749fa24cde1b411c65b50a27c76ea5b678686b15e94c",
"pubkey": "813fce4c4e76f1e7b4f4697bf1030a90f1a0b783f187d329800a4dd8697f9759",
"created_at": 1714449974,
"kind": 1,
"tags": [
[
"e",
"3dc5b00436e7355beadc0001ddb479e455c99424a01f6938143fb8dd7dca0a48",
"",
"root"
],
[
"e",
"2ac4c249596917e9bbd6beb395212bac351dd2f348b94425222a19dd9f95d43e"
],
[
"e",
"926472f53847228df1e8c1b590be6c90a23f97378042f942637712607034b3b0",
"",
"reply"
],
[
"p",
"3d2e51508699f98f0f2bdbe7a45b673c687fe6420f466dc296d90b908d51d594"
],
[
"p",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"r",
"https://bitcoinops.org/en/topics/expiration-floods/"
]
],
"content": "The attack you describe was called \"forced expiration spam\" in the original LN paper. I usually call it an \"expiration flood\". Other people have other names for it. See https://bitcoinops.org/en/topics/expiration-floods/",
"sig": "772f5d7c4baa6d49f4a557628d6c10a56253dff023682fd9bd8c0e0dc0adb9dca1143a4aa53366c18ce35be09bff24aefcac5f8bb5b98fc52cc7238c5827a6c6"
}
