goatmeal

"nodes should run on poverty computers" but also "have fun staying poor" "slightly larger blocks threaten muh decentralization" but also "I will idiotically praise cashu, boltz, and spark"

I will never be as cool as the guy who submitted the goatse ordinal. back then, the main gallery website for ordinals did not have a hiding mechanism. it appeared straight on the front page. it must have been hilarious.

you are not going to be delivered to the devil by core v30. you were already delivered to the devil in 2017 by segwit and the witness discount. luke was cheering. he cannot save you.

let's look at ordinals together. have you ever seen an ordinal before? me neither. >if filters no werk then why more OP_RETURN not happen core accidentally enabled an even cheaper data storage mechanism in 2017 when segwit was activated. now you can stuff arbitrary data into the witness and enjoy a discount. it can also take up more than 1 MB and it always creates a spendable output. some people noticed that segwit was a dangerous mess and, aiming to avoid it and fire the core devs, intentionally caused a chainsplit before it was activated. the chain without segwit is called BCH. core devs and podcasters used lies, deception, and censorship to convince people to tolerate segwit and they used lies, deception, and censorship to convince people not to use BCH. no matter what your feelings are, segwit led to the cheapest, most polluting, and most popular form of arbitrary data storage on bitcoin. everyone who said no to segwit is still waiting for an apology. >buh whatabout BSV I heard it has CSAM in it cos they let big OP_RETURN BSV is another chain forked from the BCH chain. on both chains, segwit never happened. OP_RETURN remains the cheapest option. funny how incentives work. >that's okay because someone on twitter says ordinals are not contiguous so I magically won't go to jail I think people who make the "contiguous" argument have never actually seen an ordinal before. don't worry, I think art NFTs are fucking dumb and I hadn't seen one either so you're in good company. all the data needed to construct the file is split into 520 byte chunks, but all the chunks are in one transaction. above this, it explicitly marks the transaction as an ordinal and tells the file type, so there's no plausible deniability. reconstituting the data into a regular file is simple and can be done in one line. I used txid bb6f577e30e6840dce0474f3c3c55134404688e844982a49161502d3d69e322d which contains goatse so don't do that. grep "OP_PUSHDATA2" hex_chunks.txt | sed 's/OP_PUSHDATA2 //' | tr -d '\n' | xxd -r -p > goatse.jpeg the amount of work you have to do to reconstitute arbitrary blockchain data into a normal file is almost nothing. stop pretending to be stupid. you have a photo of a man's asshole on your computer and you are sending it to other people. you are not going to convince 100% of the hashrate to avoid including ordinals, large OP_RETURNs, or multisigs with bogus outputs. you have a better chance of convincing them to join the catholic church. even at 99% it could take less than a day for an ordinal to be confirmed. do you think the guy who submitted the goatse ordinal is bothered by that? if he cared he would have used ethereum. he's probably a bitcoin maxi just like you. my point is you're FUCKED so you might as well let core optimize compact blocks and go back to talking about CTV + CSFS.

any bitcoin maxi who guffaws at this picture is a stupid hypocrite. if you run a bitcoin node, you already have illegal data on your hard drive, that you can't even prune. it's on your computer right now and you send it to other people all the time. you tell yourself excuses just like this. you implicitly agree with vitalik's radioactive autism until you delete your bitcoin node. it's time to look in the mirror. nostr:nevent1qvzqqqqqqypzqjf6tgrmu8wqdgwa9k8fg0vfyn75d8c90pt7ymmmn84aa0sqcf2hqy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpq3qw8kymlsu6ugmadfrhgftpwwsm007qpr8www2qyz4ya2smckznsapg2m4