Content-Type: multipart/signed;
	boundary="Apple-Mail=_AB33DB4F-08AC-4833-9B81-2B014E7DFCEA";
	protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <20150212074509.GC4254@savin.petertodd.org>
Date: Thu, 12 Feb 2015 09:27:22 +0100
Message-Id: <8BFAFE6A-F85B-4B89-98A0-CBBCAA67B30B@bitsofproof.com>
References: <20150212064719.GA6563@savin.petertodd.org>
	<7C171F0B-1EF8-4542-8E18-187B2E94DF14@bitsofproof.com>
	<20150212074509.GC4254@savin.petertodd.org>
To: Peter Todd <pete@petertodd.org>,
 alex.mizrahi@gmail.com
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4
Precedence: list


--Apple-Mail=_AB33DB4F-08AC-4833-9B81-2B014E7DFCEA
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C9D52640-A09B-46F2-86C7-46C34D185CDC"


--Apple-Mail=_C9D52640-A09B-46F2-86C7-46C34D185CDC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



On Feb 12, 2015, at 9:16 AM, Alex Mizrahi <alex.mizrahi@gmail.com> =
wrote:
> Why don't you use getrawmempool RPC call to synchronize mempool =
contents?



Since RPC interface does not scale to serve a multi user service.
In absence of better alternative, the interfaces used by a proprietary =
extension are usually the same as in P2P consensus.

POW is used to figure the longest chain and until now broadcasted =
transactions were assumed the one and only.=20
These simple rules ensure a consensus between the proprietary stack and =
the border router, and that is the consensus I referred to.


On Feb 12, 2015, at 8:45 AM, Peter Todd <pete@petertodd.org> wrote:
> IOW, assume every transaction your "border router" gives you is now =
the
> one and only true transaction, and everything conflicting with it must
> go.


You are right that the assumption about the one and only transaction =
have to be relaxed. Broadcasting=20
double spend only if it is actually replacing an earlier - for whatever =
reason, would simplify internal consensus logic .

Tamas Blummer
Bits of Proof


--Apple-Mail=_C9D52640-A09B-46F2-86C7-46C34D185CDC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><div><br></div><div><div>On Feb 12, =
2015, at 9:16 AM, Alex Mizrahi &lt;<a =
href=3D"mailto:alex.mizrahi@gmail.com">alex.mizrahi@gmail.com</a>&gt; =
wrote:</div><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div>Why don't you use =
getrawmempool RPC call to synchronize mempool =
contents?<br></div></div></div></div></blockquote></div><div><div =
dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div><br></div></div></div></div></div><div><br></di=
v><div>Since RPC interface does not scale to serve a multi user =
service.</div><div>In absence of better alternative, the interfaces used =
by a proprietary extension are usually the same as in P2P =
consensus.</div><div><div><br></div><div>POW is used to figure the =
longest chain and until now broadcasted transactions were assumed the =
one and only.&nbsp;</div><div>These simple rules ensure a consensus =
between the proprietary stack and the border router, and that is the =
consensus I referred to.</div></div><div><br></div><div><br></div><div =
apple-content-edited=3D"true">On Feb 12, 2015, at 8:45 AM, Peter Todd =
&lt;<a href=3D"mailto:pete@petertodd.org">pete@petertodd.org</a>&gt; =
wrote:</div><div><blockquote type=3D"cite">IOW, assume every transaction =
your "border router" gives you is now the<br>one and only true =
transaction, and everything conflicting with it =
must<br>go.<br></blockquote></div><div><br></div><div>You are right that =
the assumption about the one and only transaction have to be relaxed. =
Broadcasting&nbsp;</div><div>double spend only if it is actually =
replacing an earlier - for whatever reason, would simplify internal =
consensus logic .</div><div><br></div><div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Tamas =
Blummer</div><div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">Bits of Proof</div><div style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br></div></div></body></html>=

--Apple-Mail=_C9D52640-A09B-46F2-86C7-46C34D185CDC--

--Apple-Mail=_AB33DB4F-08AC-4833-9B81-2B014E7DFCEA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU3GPqAAoJEPZykcUXcTkcmGMH+gIHn58TpzYVm1zacZcwgXLB
sUiQWcOggc8xJtYU/ZK/kC+joNxKJ0HTR7zsJoJd3L9OBf+Pkz62mr3GzoapOJV/
3Zsoa0halA9hm3hIOzjnT6FNcECjei7xRoxlLjN44Nf8YDQFT6dfi/zyUlPTHaXX
Agj8Db71gVE0zvZtdJf0wuOq0SU6wJnc2SriqXD0kk+4Mhc8qOt5qBRimCjTxQP5
GcUIJdPt9w9cX08yCNh3BuJ9NZh5yBkTMmFN6VY2WH1g1FGawFDVr29gSXfBbQLS
B4NWa2kIZEcMQ4c61tpfHZA6OzgSmYyfsL2My/+uVbsKXlJm/qaDQMtMvo9Hlpo=
=9Vhl
-----END PGP SIGNATURE-----

--Apple-Mail=_AB33DB4F-08AC-4833-9B81-2B014E7DFCEA--