e3
Deleted Account
e39991fcbbb6a5618318cc64d3ef276d9d6741e24705c9eeaec73cd687c6c3f5
Deleted Account
Replying to Avatar goatmeal

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.

To avoid confusion, larger‑block proposals (e.g., Bitcoin Cash’s 8 MB+ blocks) pose a greater long‑term centralisation risk than the “arbitrary data” that SegWit makes possible, because the former directly inflates the resources required to run a full node, while the latter only modestly increases the effective block capacity without changing the consensus‑level data size.

nostr:nevent1qqswg6lum7vpnuks6r769shecsshpdsm2jktwm9s94ejxpkns95lx6cpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgcygqsf

Replying to Avatar goatmeal

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.

Who fuckin cares, it’s a network. You don’t stop using internet just because some dude can post his asshole through it.

Replying to Avatar Hanshan

A fuckin genius 🤯

In a world of 80IQ

Monero dumfucks still trying, even after the fact that their shitty blockchain is susceptible to reorgs organized by a basement farm colluding. Dumbfucks

This Kratter mofo is overdoing this shit. Go fuckin code your own client you stupid fuck. Knots is for dumb fucks who are driven by hysteria made up by Luke who is counting his dead babies in his profile. How stupid can one be.

Let me guess: we can inflate algorithmically and that is great for stimulating the economy.

That’s such a bright idea 😂

Replying to Avatar Hanshan

🤨

Spoken like true economists that got us to this shithole. Elasticity lmao

How the Controllers will contain Bitcoin (attack decentralization and MoE use) without heroic fights - a TLDR version

- Paperization: Deep ETFs/futures/notes to satisfy demand while pulling usage into surveilled custody.

- Tax/reporting drag: Treat any non-KYC movement as "high-friction" - 1099-style reporting, wash-sale parity, travel-rule enforcement.

- Node/Mining pool pressure: Hosting TOS, app-store policies, and insurer clauses that make policy clients the default; off-policy is niche and risky.

- MoE marginalization: Make CBDC/stablecoin rails cheaper, faster, and incentive-rich so payments gravity leaves Bitcoin as a taxable SoV niche.

- Narrative steering: "Clarity" after scares -> price pops -> users settle into paper forms; self-custody shrinks to the ideologically committed and the skilled.

In other words, contain without martyring.

- Push liquidity and convenience toward custodial wrappers (ETFs, futures, payment gateways).

- Nudge perimeters (banks/app stores/clouds/pools) to require KYC/attestation.

- Price the "sovereign" path with friction (tax treatment, reporting, limited on/off-ramps) while avoiding outright bans that create hero narratives.

This doesn't mean Bitcoin won't go up in fiat terms, of course.

What I am saying is that most people are buying gold while thinking they're buying Bitcoin.

Bitcoin is gold for most, permissionless money for few.

I don't see this trend changing as of now, however, there are falsifiers that I am tracking.

It takes just a single coordinated pool to do reorg on monero and you guys still doing shit 😂

Replying to Avatar CashDragon

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqx5tpj06sw9d57ykhh0cr699d63vc805pjvcvrcged7530a3l492s399hev nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpquwverl9mk6jkrqcce3jd8me8dkwkws0zguzunm4wcu7ddp7xc06styeczf

no thanks, I just use the real Bitcoin

works better than LN right on chain with no email or signups required

we should not need 3rd party services to send an receive Bitcoin

please do some research

https://bitcoiniscash.org/

LOL

Alby was a G

Respect for seeing through the smoke and speaking out the truth

nevent1qqs2xtqhzd3p5004yxfsrzvhy4574pktd4r4jctfrjtcq93yhzd2d2gpzpmhxue69uhnzdps9enrw73wd9hskx7clv