From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YLoxK-0007R5-F7 for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 08:17:02 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.173 as permitted sender) client-ip=74.125.82.173; envelope-from=alex.mizrahi@gmail.com; helo=mail-we0-f173.google.com; Received: from mail-we0-f173.google.com ([74.125.82.173]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YLoxJ-0008Nz-KB for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 08:17:02 +0000 Received: by mail-we0-f173.google.com with SMTP id w55so8377036wes.4 for ; Thu, 12 Feb 2015 00:16:55 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.187.236 with SMTP id fv12mr778422wjc.131.1423729015545; Thu, 12 Feb 2015 00:16:55 -0800 (PST) Received: by 10.27.148.13 with HTTP; Thu, 12 Feb 2015 00:16:55 -0800 (PST) In-Reply-To: <7C171F0B-1EF8-4542-8E18-187B2E94DF14@bitsofproof.com> References: <20150212064719.GA6563@savin.petertodd.org> <7C171F0B-1EF8-4542-8E18-187B2E94DF14@bitsofproof.com> Date: Thu, 12 Feb 2015 10:16:55 +0200 Message-ID: From: Alex Mizrahi To: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7bea40cc3a665f050edfbec8 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alex.mizrahi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YLoxJ-0008Nz-KB Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 08:17:03 -0000 --047d7bea40cc3a665f050edfbec8 Content-Type: text/plain; charset=UTF-8 > To remain useful as border router, the replace-by-fee patched core should > only relay double spend if it actually replaces an earlier transaction, as > otherwise the replace logic that is according to your commit more than just > fee comparison, would have to be replicated in the proprietary stack and > mempool might get out of sync with that of the border router. > Why don't you use getrawmempool RPC call to synchronize mempool contents? --047d7bea40cc3a665f050edfbec8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0
To r= emain useful as border router, the replace-by-fee patched core should only = relay double spend if it actually replaces an earlier transaction, as other= wise the replace logic that is according to your commit more than just fee = comparison, would have to be replicated in the proprietary stack and mempoo= l might get out of sync with that of the border router.=C2=A0

Why don't you use getrawmempool RPC call= to synchronize mempool contents?
--047d7bea40cc3a665f050edfbec8--