jimmysong on nostr

I hate how the CSAM talk distracts from the obvious:

Changing the default from 80 to 100k is reckless and unreasonable.
Allowing multiple OP_RETURNs has no real use case.
0.1 sat/vbyte is completely arbitrary.

157❤️34🤙8❤️2👍2:fire:1❤1

Jameson Lopp · 34w

Indeed, we can definitely go lower than 0.1 sat/vbyte!

Modus · 34w

I hate how a huge attack vector is treated as a distraction

Branca · 34w

Jimmy, Lopp already confess, its all about a Citrea use case that nobody ask for.

Ronin · 34w

Simple.

nostrich · 34w

https://blossom.primal.net/c2e797e2c6973620ec3039f809174d7ef7cdb336b37fa146487b8077a6514905.mov

Jerome Powell 21iQ 40TPW · 34w

Go home v30, you're drunk. https://blossom.primal.net/389b1d74e787584735789434b055401f7328dfba552ee315f3fc7e61c7dff308.jpg

🍊💊⚡️🌽 · 34w

Is that not possible Jimmy? It is germane to the conversation as a real world possibility……… They had no good reason to do this and in fact wanted to harm the protocol in this manner……. Attack vectors function in this manner…….

Simply Pu · 33w

1. There is no size of data embedding where use of anything other than OP_RETURN or the witness is preferred. Given that most node policies already allow the relay of arbitrarily large data up to the tx standardness size limits (using multiple P2SH outputs), no size limit on OP_RETURN is compatible ...