Damus
Jameson Lopp · 3w
I wouldn't fall into the purity test trap; purity tests tend to spiral tighter and tighter to the point of absurdity.
Rusty Russell profile picture
Indeed. Lightning commitment transactions stash the commitment number in the nSequence and nLocktime. Is that spam?

OpenTimestamps uses full transactions to timestamp data, is that spam?

Samurai (IIRC) had a method of obscured payment addresses which required an initial seed tx. Was that spam?

You can encode data in the key used when you use a taproot script spend path. Is that spam? (Can you tell?)
32❤️6🤙3❤️1🤔1🤙🏻1
Fromack 🏔️ · 3w
Good point. The line between 'legitimate use of blockspace' and 'spam' is entirely subjective. If you paid the fee, you used the protocol as designed. Everything else is policy, not protocol.
Toby McMann · 3w
All value is subjective!!!!
nostrich · 3w
And BIP 110 allows those use cases. New output scriptPubKeys exceeding 34 bytes are invalid, unless the first opcode is OP_RETURN, in which case up to 83 bytes are valid. OP_PUSHDATA* payloads and witness stack elements exceeding 256 bytes are invalid, except for the redeemScript push in BI...
nostrich · 3w
This is in case you have questions about Citrea. nostr:nevent1qqszcqqvg3x2fnaxrgpzv2dk08q8d9cn0ke8xlp7ewt6v472h9tt47gppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7zay9v4
BushRat · 3w
Financial transaction data is not spam on a financial transactions database. Childporn and dickbutt memes are spam. Hope that helps clear it up for you and all the other retarded pedophiles
JackTheMimic · 3w
Oh, did we recently expand those fields by ~100k bytes too? Quick answer: LN commits- No (those fields have to be there) OTS- No (also mischaracterized description They hash their message into their transaction ID, the ID length doesn't add more data) Samurai- No (a transaction to predicate, an...