Replying to Avatar Derek Ross

Hey nostr:nprofile1qqswrlemlh2wgqc4jkds3d8ueqj9a2j3gcm7r48v9tskdd6rxsd7rtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqjxamnwvaz7tmwdaehgu3wwfhh2mnywfhkx6mzd96xxmmfdejhyuewvdhk6jg4k33! I see that you've decided to join Taproot Wizards to build out CatVM which relies on OP_CAT.

The majority of supporters behind OP_CAT are Ordinals users, people that want to push it "for the memes" and "for the lawls", and a few people that I consider bad actors in #Bitcoin. I believe that OP_CAT will allow more Shitcoining on top of Bitcoin. Am I wrong?

You are incredibly talented and smart. Far more so than I could ever be. I have a deep amount of respect for you. Hell, when you were talking about building a multi-sig Lightning node for corporations while we were poolside in Madeira blew my mind. Anyways, can you help me understand why you feel that OP_CAT is needed and why am I wrong about it?

I asked nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshspg7dju about OP_CAT at the Bitcoin Freedom Festival and his short answer was that Satoshi removed it for a reason. I stopped doing research on it at that point.

Thank you brother and congratulations on the new job. šŸ¤™šŸ»šŸ«‚šŸ’œ

Shitcoining on bitcoin has existed for over a decade and isn't going away. OP_CAT doesn't uniquely enable anything more, its just a scripting proposal that enables covenants and lots of other stuff.

Current bitcoin is moving towards custodians as scaling solutions which is the opposite of what we should be doing. Covenants are a good option for trying to scale this and OP_CAT is probably the most general covenant we could get.

OP_CAT was removed from bitcoin because there was no limits on it, that could have caused DoS vulnerabilites. Bringing it back with a limit (or with GSR) would be great imo. I don't think bitcoin would be dead if satoshi instead added a limit to OP_CAT instead of disabling it.

Reply to this note

Please Login to reply.

Discussion

Go build this crap on bitcoin cash with Roger ver and everyone else who thinks they know better than satoshi

What? Satoshi made a great thing and maybe could have continued making great contributions, but i wouldn't assume that only he knows what's best for Bitcoin going forward. It's an open and decentralized protocol. Whats best is whatever increases adoptions with the least impact to bitcoins strongest properties including decentralization and fixed supply

What happened to ā€œYou don’t change Bitcoin, Bitcoin changes youā€

Just a couple short years ago Ben thought Munity was a good idea, now it’s a dumpster fire. We don’t want that to happen to Bitcoin.

Bitcoin at its base layer works and is completely fine. Go fuck around and find out on a layer 2 solution and if that’s not enough GFY and go build on a fork of Bitcoin.

Im not advocating for changing bitcoin, just pointing out that satoshi left, bitcoin has changed and the people using and developing it now are who matter.

Re: op_cat. I think the great script restoration makes sense and a lot of smart people are interested in op_cat. It's definitely beyond me, but if enough devs think its a good idea then lets see what happens.

However, i dont think everything that can be done with bitcoin as it is today has been explored and that should happen before it's changed

Nah, it's an evolving working progress, always has been. To survive it must continue to improve.

I appreciate the insight. Thanks, Ben. šŸ’œšŸ«‚šŸ¤™šŸ»

šŸ‘€

Isn’t OP_CAT a necessary capability to enable recursive covenants which would then enable permanent on-chain KYC?

Recursive covenants dont automatically enable onchain kyc.

You can do onchain kyc today with 2/2 multisig.

What pieces would be missing to implement on-chain KYC if recursive covenants are enabled?

Regarding the possibility to do it with multisig, my understanding is that it would be easier for regulators to have it implemented/enforced through recursive covenants.

The easiest way to do it is to just use custodial systems, which is the way everyone is going today.

It might make sense to support OP_CAT if Luke's filters get added to the core client at the same time so that the amount of spam could be dramatically reduced.

Otherwise I think it just creates too many variables & is likely to make serious network attacks possible.

nostr:nevent1qqs8cn4ruaxyet7yr0ahazw8phtwc3dj9h9snycgd34a3kafwuqfnvgpz9mhxue69uhkummnw3ezuamfdejj7q3qu8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhsxpqqqqqqzv7g07e

What's a scaling solution that requires OP_CAT?

It’s not about shitcoins.

How do you know why OP_CAT was removed?

As an engineer, do you think it’s a good idea to enable powerful technology IN THE BASE CHAIN that has few known limits so essentially nobody knows how it could be abused?

Satoshi’s design philosophy was clearly to limit functionality to keep the system simple and safe. He made the system robust by deliberately removing codes that might increase the attack surface of the network.

It’s not appropriate to apply start up thinking - move fast and break things - to the core system protecting the world’s money and our hope for the future.

If you’re wrong, and it somehow disrupts the underlying incentives that underpin everything … how easy is it to undo it? We can’t, can we?

How I see it:

+ Devs are humans. Even the smartest among us are not omniscient and make mistakes (eg witness discount).

+ All code has bugs. Even if the code is technically bug free, it can still change the complex incentives that make the network work.

+ We don’t have a scaling problem yet. When we do have one in the future, we should allow the pain of it to motivate innovation on upper layers so that we can avoid any unnecessary changes to the base protocol.

+ We should only allow changes to the base protocol that safely fix an existential problem that we know cannot be fixed in any other way.

+ The Bitcoin network is for many, many future generations. We need to think long term and not rush out changes to the core protocol. A decade or two to consider options is a blink of an eye in the life of the network.

Lightning is basically the only layer we can do with current bitcoin. Soft forks are needed to do more scaling. Not scaling on chain but with new layer 2 designs

Lightning is the only layer?

Umm…

1) Liquid

2) Fediment

3) Ark, and all the other R&D underway.

As an engineer, do you think it’s a good idea to enable powerful technology IN THE BASE CHAIN that has few known limits so essentially nobody knows how it could be abused?

Liquid and Fedimint are not layers, they are custodial solutions. Ark has lots of problems without covenants

I've never seen someone say concatenate is a powerful technology

Lightning is custodial too, isn’t it. No, really, think about it. What percentage of lightning usage is self-custodial? Weren’t you doing Mutiny? Does self-custodial lightning actually work for plebs?

You want to include a technology that you don’t know the limits of. If you do, please explain the limitations. Explain why it can’t be abused. Don’t you think this is something we should know?

Why do you claim to know why Satoshi removed it? What were his reasons?

I don't trust anyone that advocates for covenants. They are corrupt and pose a threat to bitcoin with their naivety.

I think it’s what separates the developers from the engineers. The engineers understand risk trade offs. The devs do their testing in production.

If we didn’t fuck up with Segwit by limiting the block size from being increased to only 1 fucking mb (which was supposed to be temporary)… which satoshi knew needed to be raised at some point in the future…

The blocksize needs to stay small. It was increased to ~4 MB and already the chain is becoming difficult to sync for small nodes. Everything has trade offs but the highest priority should be that anyone can run a node. This gives the chain the greatest potential defense against nation states.

The block size is 1mb & can be weighted 4x via Segwit…

That’s not what satoshi said…

What did Satoshi say, that we need big blocks?

Yes they intentionally put the 300kb limit & expected it to be raised in the future… where server farms are only ones who kept the blockchain fully archived…

Wasn’t it 1MB?

When you look at bcash or bsv, are you thinking we should fix bitcoin by bringing those big blocks here too?

No the 1mb limit was supposed to be temporary & was set in place during Segwit.

Scaling on chain works.

I was never a "small blocker"

No, Satoshi set the 1 MB size on 15 July 2010, many years before segwit. Link below.

The big blockers had their priorities reversed. They were ok with centralizing the chain permanently to make transactions cheaper temporarily.

If you are still a big blocker, perhaps you would find your ideological home with either bcash or bsv. Transactions are definitely cheap over there.

https://bitcoin.stackexchange.com/questions/98908/satoshi-introduced-the-1mb-block-size-limit-in-a-commit-why-did-andresen-make-a

Yes satoshi wanted to raise the blocksize early on thank you & in that exact link it clearly says it was activated during the UASF which was Segwit…

I think you should read it more closely. It says ā€œenforcedā€ not activated. That’s because it was already active in July 2010 when the code was checked in. The enforcement in Aug 2017 was the point of the UASF … to force the big blockers into a chain split.

Did you think you ā€œgot meā€? šŸ˜‚

Sometimes I get stuff wrong, but I didn’t this time.

Yeah making a git commit doesn’t merge code much less push it to the network…

šŸ˜‚

Nice try. When you say ā€œpushā€ are you referring to how Satoshi used Santa to deliver updates to nodes around the world?

Yes that is exactly what I meant

Who said we're getting op_cat?

We're getting op_cat

Might not bro

We are tho

Might not need it if they can do it without one

https://stacker.news/items/643429/

this is a brilliant on-chain shitpost by Rijndael