From: Prayank <prayank@tutanota.de>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Stumbling into a contentious soft fork activation attempt
Date: Mon, 21 Feb 2022 10:48:26 +0100 (CET) [thread overview]
Message-ID: <MwQfeUc--N-2@tutanota.de> (raw)
In-Reply-To: <guj6poK6x0q2u4ku4nmy_rhAsu33nSIyakg5-_NgAUMAOohUUjwaCgCgjHbcUqzx7Fym8AT6EsQginr9YjglDnwRpQTQwiG0sVQadp7_zhI=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Goog morning ZmnSCPxj,
Context: https://bitcointalk.org/index.php?topic=48.msg329#msg329
Maybe I should have rephrased it and quote Satoshi. I agree I should not speak for others and it was not my intention in the email.
> If Satoshi refuses to participate in Bitcoin development today, who cares what his opinion is?
I care about the opinions especially if consensus rules are not changed and remain same as far as subsidy is concerned.
> Satoshi is dead, long live Bitcoin.
I object to such assumptions about the founder of Bitcoin. Satoshi is more than a pseudonym and will stay alive forever.
--
Prayank
A3B1 E430 2298 178F
Feb 21, 2022, 14:32 by ZmnSCPxj@protonmail.com:
> Good morning Prayank,
>
> (offlist)
>
>> Satoshi
>>
>
> I object to the invocation of Satoshi here, and in general.
> If Satoshi wants to participate in Bitcoin development today, he can speak for himself.
> If Satoshi refuses to participate in Bitcoin development today, who cares what his opinion is?
> Satoshi is dead, long live Bitcoin.
>
>
> Aside from that, I am otherwise thinking about the various arguments being presented.
>
>
> Regards,
> ZmnSCPxj
>
[-- Attachment #2: Type: text/html, Size: 2139 bytes --]
next prev parent reply other threads:[~2022-02-21 9:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 1:57 [bitcoin-dev] Stumbling into a contentious soft fork activation attempt Prayank
2022-02-18 23:41 ` Peter Todd
2022-02-20 18:35 ` Erik Aronesty
2022-02-21 3:03 ` Prayank
2022-02-21 9:02 ` ZmnSCPxj
2022-02-21 9:11 ` ZmnSCPxj
2022-02-21 9:48 ` Prayank [this message]
2022-02-22 12:57 ` Billy Tetrud
2022-02-21 9:09 ` ZmnSCPxj
-- strict thread matches above, loose matches on Subject: below --
2022-01-04 11:53 Prayank
2022-01-04 14:15 ` Michael Folkson
2022-01-04 15:06 ` Prayank
2022-01-04 16:48 ` Michael Folkson
2022-01-04 17:07 ` Prayank
2022-01-04 14:42 ` Christian Decker
2022-01-04 15:45 ` Prayank
2022-01-03 2:05 Michael Folkson
2022-01-09 11:38 ` Peter Todd
2022-01-11 3:42 ` Jeremy
2022-01-11 4:38 ` Jeremy
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=MwQfeUc--N-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.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