"Keep your spam out of my mempool!"
Are you running a lightning node? What if a channel counterparty tries to defraud you by publishing an old channel state? In that case you need accurate fee estimation.
Your justice transaction will have to beat the dickbutts in miners' mempools. In order to beat dickbutts, your full node needs to know about dickbutts and what they're bidding. If you're ignorant of dickbutts you'll get fucked by dickbutts.
Login to reply
Replies (27)
Uf
Do you know of any examples of justice transactions happening in the wild? Has this scenario ever actually happened?
I'm glad my fellow biomedical scientists don't approach healthcare with attitude.
Dickbutts never occurred to me 🤔
If someone tries to publish an old channel state the chances are he'll loose all his sats.
If my justice transaction is stuck in the pool because of a sudden peak in spam (and it has), all it takes is a CPFP to get it through.
Lightning has been working like this for years without any major issues...
My guess is you're using extreme cases with very low probabilites to justify the narrative for an unnecessary change to the current consensus (which sadly makes you sound like the "dickbutt" here)
I'm just gonna leave this here for the sake of discussion


Except there are objectively less dickbutts if we keep the filters that make it more expensive to broadcast a dickbutt because you have to have or pay for a private mempool to broadcast out of band.
🤔🤔🤨
Speculation: you can't possibly know how people value their dickbutts.
Directionally correct speculation
The argument is “Should the lighting node be allowed to configure his own bone to get fucked by dickbutts?”
Yes, mom, that’s what I’m arguing about on the internet today.
Node not bone. But bone was a funny typo
Ln node operators do pay attention: They follow their earnings, adjust the channel fees, rebalance the channels when needed, check for new incoming channels and closing ones. It's not a trivial job, and improvements can be made but that is a Ln issue, not a bitcoin one.
When the "inscriptions gang of morons" were spamming the mempool with thousands of junk transactions, there was no way to adequately determine the correct fees, and txs could stay stuck for days even when they were set to mine in the next 2-3 blocks. Spamming "monkey jpgs" to everyone won't solve the problem. What we need are smarter algorithms to estimate correct fees and I believe that can be achieved even without loading all the junk into everyone's pool.
I personally believe the trade-off is not worth it, and if removing the OP_RETURN limit is not set as an opt-in option, then I will either have to patch core myself or switch to #knots. Neither of which I'm looking forward to do.
That's a rather forced example. Unilateral channel closures always have a timelock — in practice, it's at least a day, and often up to a week. That’s the window during which a justice transaction can be confirmed. In your example, you're assuming there's a high volume of spam on the network. On top of that, the spam transactions have high fees — significantly above the average for non-spam transactions, which is a critical part of your assumption. So, it's possible that the justice transaction wouldn't get confirmed within a day. But that's still quite unlikely.
In reality, spam levels are low. And that's exactly what the relay policy is for — to keep it that way. 😎
Correct, and we've seen that token mints can indeed cause extremely high fees for periods of time. It's not frequent but it's unpredictable.

Obsessed.


Would you support limiting witness data in conjunction with expanding OP_RETURN in Core then? Seems like that would prevent the situation in the first place. I understand there would be a short term dick butt spam fraud danger in this transition… is it politically impossible?
please keep spewing bullshit. free @Bitcoin Knots marketing. send the knots runners higher
Consensus changes are a lot trickier.
I'd rather us find a dynamic block size solution.
I can’t tell if you’re trolling me
😑
tail emission and dynamic block sizes fix this
the whole conversation would be much less intense.
View quoted note →
He's just encouraging everybody to switch to #knots:
Core's integrity has been compromised and the Blackrock banksters who will control the majority of coins have figured out that they need to control the network as well to control bitcoin.
They'll do this by spamming us to death. When the blockchain passes the 1TB mark, many nodes will run out of disk and shut down. They will then hardfork bitcoin to a fucked up CBDC equivalent.
"Monkey jpgs" are not a joke, they are an existential threat and must be dealt with in every possible way.
He prefers to focus on shitcoin scams
What’s the urgency for the change Jameson?
Do you see something that will render the Bitcoin network unusable?
Network seems to be doing great without any interventions…….
YOU are the dickbutt.
why are you even here?
fuck off and go retire and read something to fill the emptiness.
alternatively, go sit in the sun by a river.
the most important variable, in whatever path you choose, is that you shut the fuck up.
bellend :-)