Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D2EC4B5D for ; Thu, 5 Jan 2017 14:48:38 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F1FF318F for ; Thu, 5 Jan 2017 14:48:37 +0000 (UTC) Received: by mail-wm0-f42.google.com with SMTP id t79so485826709wmt.0 for ; Thu, 05 Jan 2017 06:48:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0NF/jRfvotLg7bbJNGb8a2VeK1xoPK7bjsU3KK2CtkU=; b=pbIgvIjTlAzE11HcG4A+6QMIii/IWNq8YuxGsF+cPsoGncz44tr+48bnCOIbUA8OWb o5MxtKzEWnTZbeHUIS6ptsU9rgC+gKXkv6qbFWzO8FGPWjEUF7GLewrjug0c0xZ5QYxr tCKIGMIFf1pizjQZ7LS2KAPa5SU7z3JDtUg9b4ii2OtlMPz8T4jQZwSfsdVAYIkAjw+f yTyeEtQqmCcSgRdW0NljK5wlTK0ksJuh6ZS5LgR9iaoNCDKZkpz8Hgb384Y3dk2AB7KI pfxe/L5lZ9wscziDHBazpuVhGV/Jr/RqAwpzqOxLLeBRCQzlRwyTxHXTA43lwefahhxI YBtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=0NF/jRfvotLg7bbJNGb8a2VeK1xoPK7bjsU3KK2CtkU=; b=QMVYgHNahcX5pqobtZSpQ4cgJdfasoCrJ3FJiCr3LZ9O5uUwO638PECsmYpedoYO9R MTMEzvHLpdQGA6pf8WfuIOyWh40Z9tD/weNQaPTqc7wxoXIQTLeeUydBYgjjzYLj4J3m tznbf55iWd7j3DiJngOpRla0P3yOdm+qHgyknuDJyiXnTxZqD5hys7es2xMxiAIXruGt 6+mRobozeU3dyBuk5W9LOwNVfSNiauk4Qb7gvSmK5PWGfeGiqIPTsWc9Yp3zVLMqPC4n 7GBzgG1vBBaWkJfEsXL6b1DwjWQNUxWrjyl1XxEYPQU0ghy5HFL6JED5L66SrnlAY1vS noMg== X-Gm-Message-State: AIkVDXJSWbxTdmjhXvdvf1S93K2lFOglaPtP+pjzfbFe/7YKHciemTnFU0WsjnaZZfJyHg== X-Received: by 10.28.178.10 with SMTP id b10mr68788778wmf.83.1483627716326; Thu, 05 Jan 2017 06:48:36 -0800 (PST) Received: from nex ([2a02:aa16:1105:4a80:8d6c:4cf3:337b:fe25]) by smtp.gmail.com with ESMTPSA id j6sm104256486wjk.25.2017.01.05.06.48.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Jan 2017 06:48:35 -0800 (PST) Date: Thu, 5 Jan 2017 15:48:33 +0100 From: Christian Decker To: bitcoin-dev@lists.linuxfoundation.org Message-ID: <20170105144833.GA5580@nex> Mail-Followup-To: Christian Decker , bitcoin-dev@lists.linuxfoundation.org References: <71d822e413ac457a530e1c367811cc24@cock.lu> <77b6dd25-0603-a0bd-6a9e-38098e5cb19d@jonasschnelli.ch> <74aeb4760316b59a3db56c0d16d11f28@cock.lu> <347a0909-affd-da0c-f7f8-09fa76bcb279@voskuil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <347a0909-affd-da0c-f7f8-09fa76bcb279@voskuil.org> User-Agent: Mutt/1.5.23.1 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Committed bloom filters for improved wallet performance and SPV security X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 14:48:39 -0000 On Wed, Jan 04, 2017 at 11:45:18PM -0800, Eric Voskuil via bitcoin-dev wrote: > On 01/04/2017 11:06 PM, Chris Priest via bitcoin-dev wrote: > > The best way is to connect to the mempool of each miner and check to > > see if they have your txid in their mempool. > > > > https://www.antpool.com/api/is_in_mempool?txid=334847bb... > > https://www.f2pool.com/api/is_in_mempool?txid=334847bb... > > https://bw.com/api/is_in_mempool?txid=334847bb... > > https://bitfury.com/api/is_in_mempool?txid=334847bb... > > https://btcc.com/api/is_in_mempool?txid=334847bb... > > > > If each of these services return "True", and you know those services > > so not engage in RBF, then you can assume with great confidence that > > your transaction will be in the next block, or in a block very soon. > > If any one of those services return "False", then you must assume that > > it is possible that there is a double spend floating around, and that > > you should wait to see if that tx gets confirmed. The problem is that > > not every pool runs such a service to check the contents of their > > mempool... > > > > This is an example of mining centralization increasing the security of > > zero confirm. > > A world connected up to a few web services to determine payment validity > is an example of a bitcoin security catastrophe. > > e > And it's a great way to tell every miner who you are and what transactions you are sending/receiving. An absolute privacy nightmare... -- cdecker