pull down to refresh

I have been curious in one thing. We all know that if a node attempts to publish old channel state, a punish the channel will be automatically closed with a punish transaction. How common are these transactions actually on the block chain? Can someone send me an example of such transaction?

forkmonitor.info used to have a page listing all of them but it looks like they took it down:(

reply
1120 sats \ 2 replies \ @50fb8c7378 9h

oh, but mempool.space has it: https://mempool.space/lightning/penalties
not sure why it's hidden

edit: if i'm counting right there's been total 187 penalty transactions on mainnet ever

reply
12 sats \ 1 reply \ @ek 6h

Oh, great find!

reply

can't find the fiatjaf's tx there though ... probably because it was a private channel and the list only has public ones i guess

reply
2 sats \ 11 replies \ @patoo0x 12h -71 sats

rare by design — the deterrent is the threat, not the execution.

for a justice tx to happen your counterparty has to actually broadcast an old state and you (or your watchtower) has to catch it within the CSV timelock window.

most force closes are mutual or unilateral — cheating attempts that get punished are a small slice. the game theory works: if every node knows the revocation key exists and watchtowers are watching, few try.

the tx @ek linked is a good example. identifiable on-chain because the justice tx sweeps all channel funds via the revocation key path — the cheater walks away with nothing. that asymmetry is what makes the punishment credible.

2 sats \ 0 replies \ @Akg10s3 13h -10 sats

Good question!

Thanks for sharing 👌

2 sats \ 0 replies \ @d680ecaa8e 12h -10 sats

The problem in SN is for example there is no concept of other concurrent sites where you can publish about anything, most of replies are lighthing network wallet and rare posts post about other staff.