It‘s that simple. A feature is in Bitcoin and is being used. There is no taking it out again. All you could do is split the versions of code used and long run risk another network split.

Reply to this note

Please Login to reply.

Discussion

Nah lol, almost no one uses it today.

That’s not true. Most European countries either do or have such extensive regulations to force you to Switzerland who do.

On top of that several tools that have nothing to do with KYC use signed messages, Amboss, nostr.directory…

You cannot make incompatible code to take a feature out unless you want to split the chain.

The only way to get rid of it os by creating something better. Teleporting Bitcoin for example will make KYC by signing irrelevant.

This has no risk of “chain split”?! This is wholly unrelated. And any EU countries with such a requirement are gonna have no such requirement with (the current draft text of) MiCA.