From: Prayank <prayank@tutanota.de>
To: emu@emuadmin.com
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th March 19:00 UTC
Date: Wed, 17 Mar 2021 09:21:39 +0100 (CET) [thread overview]
Message-ID: <MVzGeC---3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
> the last thing we need is
a rushed upgrade
Why do you think this is rushed? Speedy Trial will have few months and if UASF is required it won't involve activation immediately after ST fails. Taproot by 2022 doesn't look rushed approach IMO.
> We're not changing things that we worked out already.
Which things have we worked out that cannot be changed or not changed earlier?
> how long till we go back and change the coin supply?
Coin supply has nothing to do with soft fork activation mechanism IMO.
> I understand some of you have no patience and would like mass adoption tomorrow but those are exactly the people that do not have a say in Bitcoin development. If you want to get rich quick you do not care about Bitcoin.
Taproot activation or discussion about activation mechanism does not have 100% correlation with mass adoption. It just improves Bitcoin and helps few projects mentioned in https://en.bitcoin.it/wiki/Taproot_Uses
Nobody is talking about get rich quick schemes in Taproot Activation related meetings. At least I have not seen anyone.
> If you want faster development cycles then you have lightning to play with.
Better development cycles with less delay, less misinformation, less politics, less probability of things being exploited by mining pools or other people, organization etc. with their influence. Lightning Network is a separate project focused on layer 2 and I think it will also benefit from Taproot.
> we *DO NOT* change things we already established in the past
Interested to know who is "we" in this sentence and what are the "things" that cannot be changed.
> In order to solve the LOT debate lets give Wladimir the power to decide on his own and if he has no strong opinions he should just flip a coin.
LOT has become LOL. If this is about Bitcoin Core maintainers deciding things for Bitcoin Core, sure they already do. But users have the freedom to decide if they want to run it with default settings or use other implementation.
> MAST threshold can be even lower because it is not representative of an economic majority and it could speed up the upgrade.
Agree
> At this point involve as few people as possible and get it done. This is just about the software and the parameters of the new consesus.
Everyone should be welcome to participate in meetings, ask questions, learn more and contribute. I don't see anything wrong with it.
--
Prayank
[-- Attachment #2: Type: text/html, Size: 13426 bytes --]
next reply other threads:[~2021-03-17 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 8:21 Prayank [this message]
2021-03-19 10:45 ` [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th March 19:00 UTC Emil Pfeffer
2021-03-19 16:55 ` Prayank
-- strict thread matches above, loose matches on Subject: below --
2021-03-15 17:20 Luke Dashjr
2021-03-15 19:14 ` Jeremy
2021-03-15 19:37 ` Luke Dashjr
2021-03-15 20:59 ` Jeremy
2021-03-15 21:46 ` Luke Dashjr
2021-03-16 17:42 ` Emil Pfeffer
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=MVzGeC---3-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=emu@emuadmin.com \
/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