I didn’t. Bitcoin either is or isn’t. None of the current issue of the day changes this.

A common thread I’ve noticed amongst node runners who care about this is that their use cases for bitcoin would be just as well served by setting blocksonly=1 in bitcoin.conf…

Not yummy. 0/10 recommend, regardless of what Klaus says.

Bitcoin is either censorship resistant or not. Can’t know until there is a good reason to attempt censorship. Apparently the CSAM that has been in the chain since forever isn’t enough of a test, I guess.

See next iPhone and AirPods…ostensibly solves this issue.

Reminds me of Aslan’s command to a young girl in book 6 of the Chronicles of Narnia: “I lay on you this command, that you seek this lost prince until either you have found him and brought him to his father’s house, or else died in the attempt, or else gone back to your own world.”

That’s a lot more complex than my mental model of my car!

Governments look at bitcoin and think “do we want an inflexible monetary policy?”

They view adopting bitcoin as a choice they have to accept and reject and they of course reject bitcoin in favor of having a money printer.

But that’s improper framing…they eventually won’t have a money printer because what they print won’t be money forever.

You can like just not relay stuff…blocksonly = 1

#knots

Making data storage hard via op return relay limit made sense when there was no easy alternative to opreturn.

That said, I can find no reason why eliminating configuration option is preferable to changing default from 80 to 160 bytes. Not convinced 100,000 bytes will be used for financial transactions but 160 would for Citrea’s use case (to the extent I understand it).

HFSP. If you can’t understand it or don’t believe me I don’t have time to explain it to you.

Don’t get me wrong, I run knots. But I know it doesn’t matter what I run and I know core making this change doesn’t matter either. Shocking but relay policy isn’t consensus.

Agreed. I don’t believe bitcoin should be used for spam. And I don’t think ripping the bandaid off opreturn is wiser than a stepwise increase of defaults, but the whole CP/CSAM argument is moot.

Inspired by, written by…

I drank hose water routinely in the summer because nobody went home for lunch, I’m sure that qualifies me.

Yup. And people use inscriptions because opreturn wouldn’t relay. And inscriptions bloat the Utxo set, unlike opreturn spam which can be discarded.

Raw form, like everything. But it’s in more than one transaction. Is that enough obfuscation? Would need a command like

bitcoin-cli getblock 00000000000000ecbbff6bafb7efa2f7df05b227d5c73dca8f2635af32a2e949 0 | tail -c+92167 | for ((o=0;o<946;++o)) ; do read -rN420 x ; echo -n ${x::130}${x:132:130}${x:264:130} ; done | xxd -r -p | tail -c+9 | head -c184292 > bitcoin.pdf

But anyone telling you how to do it will be documenting their crime for you.

Opreturn changes won’t change the fact that a command would be needed to make people aware of the illegal numbers on their nodes.

I’m totally in favor of knots existing and letting people set any relay policy they want…because sometimes choice matters in ways that are completely meaningless on a technical level…

In some ways, by not slowly raising default settings, core is diversifying implementations and I’m happy about that.

If anyone really cares about CP relay and the downsides of having such vastly disparate mempools, they could ref write the mempool to keep metadata about valid but spammy transactions each node decided to drop…this way people still can calculate fees properly without participating in spam / CP relay / download until it’s in a block.

Let me spell this out more slowly for you: out of band payments ( like via slipstream ) won’t go to big and small miners alike.

Do you see it now? Big miners get paid more and can stay profitable longer as revenues decrease.

Nobody uses inscriptions on purpose. They do so because opreturn requires slipstream payments and they don’t want to pay slipstream and would rather pay more to stuff it in opreturn (out of band payments cause miner centralization)

Exactly. Making it 83 or 85 or 160 wouldn’t be an issue either way. Obliterating it might be unwise.

I’m not happy with Core removing a configuration option. I don’t see the advantage of removing configuration option over bumping the default to 160 bytes, for example. I think the CSAM is a nonsense argument, but slowly ramping up op return size in relay policy may be wise for technical reasons.

HFSP

Rush. It’s a few miles west of there.

Hope you didn’t spend all that time at UofC for treatment! But if so, I hope you’re well now!

If you think bitcoin can only ever be digital gold/a store of value, I’d say you’re not thinking big enough. Bitcoin is this and more.

If guns are outlawed, then I’ll become an outlaw.

Got it.

I imagine the truth most properly expressed woul look like a table comparing low resource full node performance with and without spam vs. Block height

Something like: rpi3 nodes will become impractical at blockheight xxxxxx with spam but will remain practical until xxxxxx+yyyyyy without spam or something like that.

I was there…and it was amazing…

On the same continent I mean. nostr:npub1fceadcz5zunfrxkv33437e27z86tehs95gtc4z7wjkeexel8llrq50sy0m

Well, I for one would gladly put nostr:npub1el3mgvtdjpfntdkwq446pmprpdv85v6rs85zh7dq9gvy7tgx37xs2kl27r's boobs on my chest 🥳🍾

Another Hell thread? Well, it’s hard to argue or be unhappy about boobs, so there is that on the + side.

Welcome to the Wild West my friend

Short video shows sad things. Is there a longer video?

Fact check: true ✅

But this is not boobs. This is obesity induced gynecomastia…there is a real and genuine different between this and real boobs. Trust me. I know.

Fantastic podcast

nostr:note1e63g34tvmhcv7d9cjmnt7z3jsvu0t4f0fr34jn2tnhs98cz5gc9szv2rs9

I was just proud to be tagged near nostr:npub1el3mgvtdjpfntdkwq446pmprpdv85v6rs85zh7dq9gvy7tgx37xs2kl27r's nipples. Makes me feel special 😂

Aussie bitcoiners are badass. If you’ve never been to a nostr:npub1fceadcz5zunfrxkv33437e27z86tehs95gtc4z7wjkeexel8llrq50sy0m https://bitcoinbushbash.info, you are really missing out.

How does one get to a bush bash? It takes work. These are not held in easy to get to places with the intent of keeping the riff-raff out…and it works. Sure, it takes proof of work to get there, but the quality of the hearts and minds present is second to none.

So, how do you get to a Bush Bash? Do you need an invite, like Satoshi Roundtable (which I’ve been to twice and it was great)? Nope.

Do you need a $3,000 VIP BTC Prague ticket (been there, done that)? Nope.

Do you need to register? Nope!

Just show up. If you can get there, you’re almost certainly legit.

Reminds me of a bigger version of the hyper local bitcoin bitcoin meetup I went to in Minneapolis in 2013…same energy and same curiosity and enthusiasm.

Busselton, WA – Fri 31st Oct → Sun 2nd Nov – Shelter Brewery

Parkes, NSW – Fri 28th → Sun 30th Nov – Cooke Park Pavilion

Also, meat in Australia is beyond good. Their beef is as good as US beef, but their lamb is far far better…and of course kangaroo as a delicacy is beyond delicious, even if a little hard to come by.

If anyone wants to go to Palm Cove in 2026, shoot me a message. I want to bring my wife and kids next year.

Meh. BNB will fall to use case value in time. Which isn’t extremely high. He can’t unload it quickly and will have to unload slowly to keep price high.

The place to be last night was Palm Cove for nostr:npub1fceadcz5zunfrxkv33437e27z86tehs95gtc4z7wjkeexel8llrq50sy0m for sure.

Because the CIA forgot to get a warrant to listen to your EMF instead of just your voice :)

Love it. I’ve got a good nose for the few good conferences out there

Of course