MIME-Version: 1.0
References: <6D57649F-0236-4FBA-8376-4815F5F39E8A@gmail.com>
	<CADZtCSgKu1LvjePNPT=0C0UYQvb47Ca0YN+B_AfgVNTpcOno4w@mail.gmail.com>
	<CDAFC2F7-A0AD-460B-B5B1-A717F7EC700E@gmail.com>
	<CAO3Pvs_gvYy99Bch=7RwVszM_0PFTKUyqDVok=xfm4OOcqwaaQ@mail.gmail.com>
	<6D36035C-A675-4845-9292-3BC16CD19B41@gmail.com>
	<CAO3Pvs_Ai9d_uHC2a3ndGXhBoV-PDp2y_NShkbn=hRuzu=wNFw@mail.gmail.com>
	<5A850549-B6C9-4590-BA9B-0D69BBE531F9@gmail.com>
	<CAAS2fgRY-EaPMORjipJuysi-z61VUMivOKmSeO1Rv7vXOPeLKQ@mail.gmail.com>
	<CAGc5dgbm0wQKs4bAyN8bPdqq=RbS--TvcvUOmX2_rMTCx0POAg@mail.gmail.com>
	<CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
In-Reply-To: <CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
From: Tamas Blummer <tamas.blummer@gmail.com>
Date: Wed, 6 Feb 2019 21:17:17 +0000
Message-ID: <CAGc5dgZOGZh61TZL1YghqnGez59psyhfSz1tv3KcbS6dgp8cww@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ee02d40581404015"
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
Precedence: list

--000000000000ee02d40581404015
Content-Type: text/plain; charset="UTF-8"

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?
>

--000000000000ee02d40581404015
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>The attack was in your implication that I would assu=
me=C2=A0 ill intent of those contributed to the proposal. That is not my po=
sition. I explained why, I think, rolling out a commitment could face oppos=
ition. This foreseable opposition, that must not come from you makes me pre=
fer a provable uncommitted filter for now.<div dir=3D"auto"><br></div><div =
dir=3D"auto">I am myself concerned of the implications if many nodes would =
blindly follow POW.</div><br>I did restart the discussion which I read and =
participated in at its first instance because implementing the current prop=
osal taught me how problematic as is until not committed and because I have=
 not seen a sign to assume commitment was imminent.</div><div dir=3D"auto">=
<br></div><div dir=3D"auto">This is not just missing code. AFAIK we do not =
even have a consensus on how any future soft fork would be activated.=C2=A0=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">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.</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">I and others learned in this new d=
iscussion new arguments such as that of atomic swaps by Laolu. If nothing e=
lse, this was worth of learning.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">It appears me that it is rather you assuming ill intent on my sid=
e, which hurts given that I do contribute to the ecosystem since many years=
 and have not ever been caught of hurting the project.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Tamas Blummer</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto"><br><div class=3D"gmail_quote" dir=3D"auto"><div dir=
=3D"ltr">On Wed, 6 Feb 2019, 20:16 Gregory Maxwell &lt;<a href=3D"mailto:gm=
axwell@gmail.com">gmaxwell@gmail.com</a> wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On Wed, Feb 6, 2019 at 7:48 PM Tamas Blummer &lt;<a href=3D"m=
ailto:tamas.blummer@gmail.com" target=3D"_blank" rel=3D"noreferrer">tamas.b=
lummer@gmail.com</a>&gt; wrote:<br>
&gt; I do not think this ad hominem attack of you on me was justified.<br>
<br>
I apologize if I have offended you, but I am at a loss to find in my<br>
words you found to be an attack. Can you help me out?<br>
<br>
On reread the only thing I&#39;m saying is that you hadn&#39;t even read th=
e<br>
prior discussion. Am I mistaken?=C2=A0 If so, why did you simply propose<br=
>
reverting prior improvements without addressing the arguments given<br>
the first time around or even acknowledging that you were rehashing an<br>
old discussion?<br>
</blockquote></div></div></div>

--000000000000ee02d40581404015--