From: Tamas Blummer <tamas.blummer@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Jim Posen <jimpo@coinbase•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Interrogating a BIP157 server, BIP158 change proposal
Date: Wed, 6 Feb 2019 21:17:17 +0000 [thread overview]
Message-ID: <CAGc5dgZOGZh61TZL1YghqnGez59psyhfSz1tv3KcbS6dgp8cww@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]
The attack was in your implication that I would assume ill intent of those
contributed to the proposal. That is not my position. I explained why, I
think, rolling out a commitment could face opposition. This foreseable
opposition, that must not come from you makes me prefer a provable
uncommitted filter for now.
I am myself concerned of the implications if many nodes would blindly
follow POW.
I did restart the discussion which I read and participated in at its first
instance because implementing the current proposal taught me how
problematic as is until not committed and because I have not seen a sign to
assume commitment was imminent.
This is not just missing code. AFAIK we do not even have a consensus on how
any future soft fork would be activated.
While trying to build a useful software I have to make assumtions on the
timeline of dependencies and in my personal evaluation commitment is not
yet to build on.
I and others learned in this new discussion new arguments such as that of
atomic swaps by Laolu. If nothing else, this was worth of learning.
It appears me that it is rather you assuming ill intent on my side, which
hurts given that I do contribute to the ecosystem since many years and have
not ever been caught of hurting the project.
Tamas Blummer
On Wed, 6 Feb 2019, 20:16 Gregory Maxwell <gmaxwell@gmail•com wrote:
> On Wed, Feb 6, 2019 at 7:48 PM Tamas Blummer <tamas.blummer@gmail•com>
> wrote:
> > I do not think this ad hominem attack of you on me was justified.
>
> I apologize if I have offended you, but I am at a loss to find in my
> words you found to be an attack. Can you help me out?
>
> On reread the only thing I'm saying is that you hadn't even read the
> prior discussion. Am I mistaken? If so, why did you simply propose
> reverting prior improvements without addressing the arguments given
> the first time around or even acknowledging that you were rehashing an
> old discussion?
>
[-- Attachment #2: Type: text/html, Size: 2657 bytes --]
next prev parent reply other threads:[~2019-02-06 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:41 Tamas Blummer
2019-02-04 20:18 ` Jim Posen
2019-02-04 20:59 ` Tamas Blummer
2019-02-05 1:42 ` Olaoluwa Osuntokun
2019-02-05 12:21 ` Matt Corallo
2019-02-06 0:05 ` Olaoluwa Osuntokun
2019-02-05 20:10 ` Tamas Blummer
2019-02-06 0:17 ` Olaoluwa Osuntokun
2019-02-06 8:09 ` Tamas Blummer
2019-02-06 18:17 ` Gregory Maxwell
2019-02-06 19:48 ` Tamas Blummer
[not found] ` <CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
2019-02-06 21:17 ` Tamas Blummer [this message]
2019-02-07 20:36 ` Pieter Wuille
2021-10-03 9:53 ` Dustin Dettmer
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=CAGc5dgZOGZh61TZL1YghqnGez59psyhfSz1tv3KcbS6dgp8cww@mail.gmail.com \
--to=tamas.blummer@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmaxwell@gmail$(echo .)com \
--cc=jimpo@coinbase$(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