RocketNode on Nostr: I only run the calc once, when the FC is mined. Sometimes it’ll include a htlc ...
I only run the calc once, when the FC is mined. Sometimes it’ll include a htlc sweep if it makes it to my mempool before I calculate the fees for the FC (pretty rare). But the bot already posts A LOT and there’s still over 1k FCs in the mempool.
The main problem is the expiry/delay isn’t known from the raw FC tx and not everyone runs a node that will stage 1 sweep immediately. And I believe most implementations won’t stage 2 sweep at a loss. So the backlog of unfinished FCs that needs to be tracked will grow.
Maybe if the mempool ever clears up, I can do some sort of post mortem analysis since I do keep a record of all the FC txids.
Published at
2024-01-01 03:51:52Event JSON
{
"id": "dac141db75a1b85c00a3ebefba6a6ce43d343d7dcc3c085ca1aacf1ce32a5b08",
"pubkey": "1bf168ac47a23f1d391e8bd77b4758d189fc6b1def5208189a0e68e01c87426e",
"created_at": 1704081112,
"kind": 1,
"tags": [
[
"e",
"dd23b72312cbbcf98ea6f7f87ca128f78fdd4c5b4cc612324b296954cc995d6d"
],
[
"p",
"54eb734c9375f404fb4c069638c2dd870c32b81db8b2c1d36fa4ab511e367fb5"
]
],
"content": "I only run the calc once, when the FC is mined. Sometimes it’ll include a htlc sweep if it makes it to my mempool before I calculate the fees for the FC (pretty rare). But the bot already posts A LOT and there’s still over 1k FCs in the mempool. \n\nThe main problem is the expiry/delay isn’t known from the raw FC tx and not everyone runs a node that will stage 1 sweep immediately. And I believe most implementations won’t stage 2 sweep at a loss. So the backlog of unfinished FCs that needs to be tracked will grow. \n\nMaybe if the mempool ever clears up, I can do some sort of post mortem analysis since I do keep a record of all the FC txids.",
"sig": "bad6a3c919833e368eb910b96c6bc7270b8ee1ffd7550f0c77deaf76a9619769c4afdfaba6988c23f1a2e2ebd2452fc61c342f8b29c920f7b385c1268145cf0b"
}