From: Prayank <prayank@tutanota.de>
To: luke@dashjr.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CTV BIP review
Date: Tue, 18 Jan 2022 23:20:45 +0100 (CET) [thread overview]
Message-ID: <MtjGn81--7-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Hi Luke,
This is the first competent review for CTV based on my understanding. I would not mention controversial things in this email but nobody cares about scammers and we will review everything irrespective of personal or legal attacks on developers because some people are prepared for it and capable, competent and healthy.
> nit: Poorly phrased. Even simple scripts can do that already.
Agree
> I would ideally like to see fully implemented BIPs for at least one of these (preferably the claimed CoinJoin improvements) before we move toward activation.
Agree
> Hard NACK on this. BIP 9 at this point represents developers attempting to disregard and impose their will over community consensus, as well as an attempt to force a miner veto backdoor/vulnerability on deployment. It should never be used again.
Agree
Other technical comments on BIP are appreciated however they would be better answered by Jeremy at this point or other as I am still researching and not confident to comment.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 1682 bytes --]
next reply other threads:[~2022-01-18 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 22:20 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-18 21:19 [bitcoin-dev] CTV BIP review Luke Dashjr
2022-01-18 22:02 ` eric
2022-01-18 22:09 ` Luke Dashjr
2022-01-18 23:00 ` eric
2022-01-19 12:02 ` Michael Folkson
2022-01-20 15:23 ` Billy Tetrud
2022-01-20 22:03 ` eric
2022-01-21 17:36 ` Billy Tetrud
2022-01-18 23:54 ` Jeremy
2022-01-19 0:37 ` Alex Schoof
2022-01-20 18:38 ` Anthony Towns
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MtjGn81--7-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox