From: Prayank <prayank@tutanota•de>
To: Emil Pfeffer <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: Fri, 19 Mar 2021 17:55:27 +0100 (CET) [thread overview]
Message-ID: <MWAPRNh--3-2@tutanota.de> (raw)
In-Reply-To: <20210319104544.l4z6shndm2xnmk77@www01.emuadmin.com>
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
> back in the day we also had people that thought 10 min avg block time is too much.
Not sure what some people thought about block time interval has to do with me. Also these are the things written by Greg Maxwell and Chris Belcher about it that I agree with and been sharing from sometime now on many platforms:
https://twitter.com/prayankgahlot/status/1269164956899049474
https://bitcoin.stackexchange.com/a/103289/
> Starting from the parameters of bitcoin consensus to the way Bitcoin Core is organized to the minimum time of 18 months an upgrade needs to last. (based on prior experience) If you want to challenge any of the old rules it takes more than ignoring them and doing whatever you feel like (is useful to get the result you want (again the tyrant theme)).
I was assuming Bitcoin is a protocol for p2p decentralized network and Bitcoin Core is just one implementation which is used by most of the people for lot of reasons but things can be improved and I am hopeful will improve with time. Users were, are and will be free to run whatever they feel like: Bitcoin Core or fork of Bitcoin Core or Other implmenations but still use Bitcoin.
> You seem to believe that there exists some entity that gets to decide what goes on and gets to exclude anyone it wants from the decision making process.
No I don't. You seem to have lot of assumptions. My comments were expectations from the people who are more experienced than me and know more about Bitcoin development. Things can change, you can always go out of the box to improve things.
> "we" is a reference to "we're all Satoshi" and the "things" you will learn by learning the past.
Satoshi if was a person and not group would be disappointed about few things but anyways. "We" should not discourage people from discussion about soft forks that everyone agrees will improve Bitcoin. I don't know everything about past but again thanks for the assumptions.
> If the meeting is about making progress on an issue very few people have any clue about then it is desirable that the people that are looking to learn should do so using other venues.
Any suggestions which venues will work better for Taproot related meeting that you don't have issues with?
--
Prayank
[-- Attachment #2: Type: text/html, Size: 2940 bytes --]
next prev parent reply other threads:[~2021-03-19 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 8:21 Prayank
2021-03-19 10:45 ` Emil Pfeffer
2021-03-19 16:55 ` Prayank [this message]
-- 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=MWAPRNh--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=emu@emuadmin$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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