Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support indicated: No #52

Open
arbadacarbaYK opened this issue May 7, 2022 · 1 comment
Open

Support indicated: No #52

arbadacarbaYK opened this issue May 7, 2022 · 1 comment

Comments

@arbadacarbaYK
Copy link

As a merchant and user i expect features, that might open doors to restricting the use of bitcoin in unforeseable ways, to not end up being pushed that fast and I do not like the idea you talked about at MIT to involve the blockchain to support a lot of speciality use cases in the future as well.
So far not even taproot is fully implemented everywhere and it was integrated quite a while ago.
I see this as a distraction in focus on what the blockchain should be.

I do see a certain need for the features but I do not see any of them as urgent nor belonging where you want them.

@reardencode
Copy link
Collaborator

Confirming that you still want to signal no?

For what it's worth, CTV cannot be used to restrict anyone's bitcoin without their express consent (i.e. by them creating an address with a CTV restriction). In this way it works exactly like CLTV or CSV - only the recipient can apply it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants