Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1815240F for ; Thu, 5 Jan 2017 07:45:14 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F79312C for ; Thu, 5 Jan 2017 07:45:13 +0000 (UTC) Received: by mail-pg0-f49.google.com with SMTP id y62so185310651pgy.1 for ; Wed, 04 Jan 2017 23:45:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=voskuil-org.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=GoUMSnuvT5KIXsWzohP/4cKUzTbiynt3eXZpzdGgtCA=; b=a0ZD8MY6Gh/gYSRIN+qUiDHS4jZ8dky7gxJ1qOgDe4YtGcwdRHogkvdiXMkjI+NoSv V7fSRtgG3RdYIXfgkgFGbkzb6sMSMb2XZ5Difqbd21JjwW4UtXKBDMYDAXo0Cy3o5apF Tb5RxU0msOOzgNx4Gt6ARTTMlc15ZXqpyDzLxodF3oUHuifYjzSOSfgBoIXDjrjIidgl gjDWMuNuifn9znxPw2k9y4+HxmxRrMs8pNgTryi22P4lLAeowWJz5cocFoTy1Sh+u31h 0+Gkd7uUYimzvG6X9rbtjys6ZHQDdM/yeB0yQ8tw63JvJQEFFvBvUuN6CftJL8fbcOZ8 fMNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=GoUMSnuvT5KIXsWzohP/4cKUzTbiynt3eXZpzdGgtCA=; b=EbH9vB9If52NLfr8H4HOwImiuq13nlHSHERD0s1xIJxglKcIFyQTCg79FQvXmWGLcG OvVDRA5CueTLmj89GZBFo2BdNZWKLHHhcCFd6/aXTdTQlWHGW6JQVkPKM+XNpSdNSjSp L4C0Se3E6A7e8R0eJ0vnx9a2n0vQm4Vv7Wk52awgcf7ZB3nSp0uxH9m4NXNTS2uOPZaX NMkjwi1P1YxVIuvCr1UCex8qtgOpwuxE8HbYQEN2QhHkqUOK84ViFErQLhCWXj1Qf28G C9/4Uq0QGuFIXdgwMK88aUe+1yZyKEgeE+ucq3x5/Zzz1MK+2g20Gu9T1shoPYP6IFNG j1vw== X-Gm-Message-State: AIkVDXLk3iJy16irWyxeSkotZZ0EXDJspsOa7XP9ivd9MzjUt633Qd7W5Odcf7IjTy0TVQ== X-Received: by 10.99.222.85 with SMTP id y21mr130754306pgi.119.1483602313251; Wed, 04 Jan 2017 23:45:13 -0800 (PST) Received: from ?IPv6:2601:600:9000:d69e:118b:d57:1967:d8f1? ([2601:600:9000:d69e:118b:d57:1967:d8f1]) by smtp.gmail.com with ESMTPSA id o68sm151377774pfb.42.2017.01.04.23.45.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 23:45:12 -0800 (PST) To: Chris Priest , Bitcoin Protocol Discussion , Jonas Schnelli References: <71d822e413ac457a530e1c367811cc24@cock.lu> <77b6dd25-0603-a0bd-6a9e-38098e5cb19d@jonasschnelli.ch> <74aeb4760316b59a3db56c0d16d11f28@cock.lu> From: Eric Voskuil X-Enigmail-Draft-Status: N0110 Message-ID: <347a0909-affd-da0c-f7f8-09fa76bcb279@voskuil.org> Date: Wed, 4 Jan 2017 23:45:18 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pufegsgo9fmwqGIOnwjBAlr9Nbe0Dul4B" X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 05 Jan 2017 13:11:20 +0000 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 07:45:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Pufegsgo9fmwqGIOnwjBAlr9Nbe0Dul4B Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/04/2017 11:06 PM, Chris Priest via bitcoin-dev wrote: > On 1/3/17, Jonas Schnelli via bitcoin-dev > wrote: >> >> There are plenty, more sane options. If you can't run your own full-no= de >> as a merchant (trivial), maybe co-use a wallet-service with centralize= d >> verification (maybe use two of them), I guess Copay would be one of >> those wallets (as an example). Use them in watch-only mode. >=20 > The best way is to connect to the mempool of each miner and check to > see if they have your txid in their mempool. >=20 > https://www.antpool.com/api/is_in_mempool?txid=3D334847bb... > https://www.f2pool.com/api/is_in_mempool?txid=3D334847bb... > https://bw.com/api/is_in_mempool?txid=3D334847bb... > https://bitfury.com/api/is_in_mempool?txid=3D334847bb... > https://btcc.com/api/is_in_mempool?txid=3D334847bb... >=20 > 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... >=20 > 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 --Pufegsgo9fmwqGIOnwjBAlr9Nbe0Dul4B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJYbfmOAAoJEDzYwH8LXOFOOT8IAJ7BOf01WmHew4xSJ9LPs6e8 6Dg9snnuai4epdbRW/+kkH85YCpG+LeoiD5uqJIKt8YgdCTaWjG4M6rACCF5P92I gzTbD6nCEIvWUvuX5tjWOHPEDSTaASFOwHXmNJr1RBNycJyajCfPX5Cgg89EMeOO 3nc1Crp/3gyxrY105gm0B7niC/sY/k1jBJ1PubW/vQN0maHQ5xaf7+DmBjqN6D/1 SAZaOcpBIPay2sb7zl+NI+kwwQW8Sc2ahqgY9eaiYmWtIcYubhSQKjZ9HYdV7dLd J4u3ilVBObj3LQB/Rz/UdESzHcS0Vo04FPcO+U8nXRl1v+wx4nkK26WvclxeSmQ= =cnM0 -----END PGP SIGNATURE----- --Pufegsgo9fmwqGIOnwjBAlr9Nbe0Dul4B--