Need to watch

Did you mean to post Alex’s own article on MEV or was the “in case you forgot” a joke about that?

Oh, my! Bless your heart. I guess you don’t know how to respond when your usual bullying stops working.

The only feeling I’m getting is that cringe one where you’re watching someone in the movie embarrass themselves. And also starting to feel a bit sorry for you.

I explained to you how there is a risk of MEVil. I guess you can just pretend I never said it. Everyone else can see that I did and also see that you had nothing to say.

I got a nice glass of wine 🍷 here. I’m going to take a drink every time you say “feelings”. Don’t keep me waiting! 😆

I read you correctly, didn’t I? 😎

I look forward to your actual rebuttals when you have some.

You didn’t show anything. You just made claims I didn’t know what I’m talking about. Ad hominem attacks are always the fallback, aren’t they?

It’s not on me to prove it’s necessary and safe. It’s on those advocating for it. And apparently that’s not you. 😂

Do you just jump into random convos and yell “you don’t know what you’re talking about!!” And then refuse to support you point when challenged? Pretty funny. 😄

Is CTV being used the wild right now? In Liquid? Somewhere else?

Hard for me to trust “it’s the same as” arguments because if it were the same then we wouldn’t need it.

Is there a document somewhere that provides an in depth review of the safety considerations?

What is the feature that it provides that you care most about?

This summarizes my lates thoughts. Important to also prove necessity.

nostr:note16zakjweexcw9hjawwxllrj702mnt3k9ve69lgq5am39q77vedzksnd8n4a

Great, I’m glad someone who does just showed up. Go ahead, tell me all the ways it can be used, and prove it’s both technically safe and also doesn’t disrupt the network ecosystem.

Primal shows in sidebar. I designed UI for mobile but no mobile client has implemented it yet

I’m not in favor of generic expanded capabilities to the core protocol where we don’t know the limits of how they will be used.

It would be better, IMHO, to pick specific use cases that the community wants and to then engineer the best, most limited change that meets that need. Vaults? Payment channels? Etc. We should design a change to do just that and only that.

We need to learn our lesson with Taproot and discounted witness data. Devs didn’t realize how it would be used for spam.

Devs aren’t omniscient and can’t predict all ways a change can be abused. Some of the abuses will even be indirect and attack the incentives underpinning key operations (like mining). Best to lock it down to reduce the attack surface area.

Thats a fair argument and I don’t pretend to know about all the different options. I’ll check out the Brink episode. Thanks for the suggestion.

Who wants to help with a Core fork CTV client with a 2 year activation flag day? With a 90% support for early lock in.

There’s just no other proposal that has the length of testing, use, and extremely clear limits as CTV. It’s 100th the change that taproot and Segwit were and it just feels silly that we’re just sitting around waiting. At least starting something so people will discuss it seems like the way forward, imo. #Bitcoin

It's time for a culture shift in Bitcoin and I can see it happening.