tee8z on Nostr: After listening to the lastest Rabbit Hole Recap just want to state it's not trivial ...
After listening to the lastest
Rabbit Hole Recap (npub10ut…xdlq) just want to state it's not trivial to do accounting on lightning nodes. There are edge cases that get hairy around on-chain and lightning fees, can be done but typically requires an external service/added plugin to keep track of your lightning node's historical data and plugging in information from on-chain to get a full picture. The node software itself tries to limit the amount of state it keeps so that it can operater better and stay leaner. This is a bigger problem for larger nodes that have had a ton of state go across them. Just my 2sats
Published at
2024-02-10 01:08:06Event JSON
{
"id": "8501b7b4536962fd6396868a7ab0753ba84feac4c8d1f2df839b0087af9919d0",
"pubkey": "8ae75ae2d75a7da1ed11572059cbae2674eebc7fb2cbea60b83d98f1c162214d",
"created_at": 1707527286,
"kind": 1,
"tags": [
[
"p",
"7f177706ad6e0aea75a9e3345d9ffdae67676faff249be657b596375e1ced391",
"",
"mention"
]
],
"content": "After listening to the lastest nostr:npub10uthwp4ddc9w5adfuv69m8la4enkwma07fymuetmt93htcww6wgs55xdlq just want to state it's not trivial to do accounting on lightning nodes. There are edge cases that get hairy around on-chain and lightning fees, can be done but typically requires an external service/added plugin to keep track of your lightning node's historical data and plugging in information from on-chain to get a full picture. The node software itself tries to limit the amount of state it keeps so that it can operater better and stay leaner. This is a bigger problem for larger nodes that have had a ton of state go across them. Just my 2sats",
"sig": "fec5c299f6f81b5491025f47a4daa6115565527d0017c910cfce4a88e08849561ee13af7834dac2085d012aef74b9ab4b53bda89f5d2a6099d29087cd7d08862"
}
