From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AF39692B for ; Thu, 5 Jan 2017 07:06:39 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-oi0-f66.google.com (mail-oi0-f66.google.com [209.85.218.66]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E2DC013A for ; Thu, 5 Jan 2017 07:06:37 +0000 (UTC) Received: by mail-oi0-f66.google.com with SMTP id 3so49007774oih.1 for ; Wed, 04 Jan 2017 23:06:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=P41Z4BmqdJ4aEx0+o3ht3WDGlejuRG3uElckPSV6uhI=; b=nLOouT9PajnkDNzFH04rxjJZmOJR8p3V1rOKrPr1wadgv/wpY2eH2GiGHZTbfAfV4M twNkrJpx5OAag0s9sU5Zx5y6g/6i3jGIyIaFYRi8U+PC6jjgBacRkAUUMn9tR8x2S8Nb VTVU3+2byQ7DQ13/ZxBAonafPy/P/NA8k45Knusn01iZOB+XYuxVvOim4/HcrbfyH+Zr Wv/BCyBhfDaYbgY3hjFAVPLfD9c5BggkH4ICfpxQ4YIWHZlZbcsMsQgSqticecrvBVm1 szChqflxshRItXvrQXp0aJrDRdx/m8fC9BVpgGsqO1SzVRPE5IKiQEJL5SSCXO27WNzw ayrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=P41Z4BmqdJ4aEx0+o3ht3WDGlejuRG3uElckPSV6uhI=; b=bMjPl+YikpMmxcxl3AGpeDGu9198t8iROdPJJ7H6P+wUEYaeyVBCSoSjI8sWTBHKFs 2f0JB+9Lr40mG62s6qP2a+Nu1rcQ3lnBNZXr3TnZxcJkKxT2N7NprdYGjo0HzgSg/ZOz Rchse8hnzPWqD1e/RuHrZbzHHRvpmXvRCBkEDJhc0I8s9llUhefYQV2OnM9zkjbYy9RO kF0mKiGYVmcjyX8r3vYOL/B3/T9FUElVfnGeNiQYpvSSUylVMoa70JAeg7+vMi1gtUch QcMRdr8TTn/Mw+dJ81rWeX63Xk7Fr2CFOvMKgyxhDpRxmS9/SMaV5Js5qITwLjMbhyq9 0O3g== X-Gm-Message-State: AIkVDXJ0k5M2xs1/GVRudaNTcDt5Kk43S35bUibQ2i0+SwOnioXLBHHkkVC5lFqSD0gIYzbq1B4L7JDWK9PuiQ== X-Received: by 10.157.35.35 with SMTP id j32mr32479306otb.90.1483599997182; Wed, 04 Jan 2017 23:06:37 -0800 (PST) MIME-Version: 1.0 Sender: nbvfour@gmail.com Received: by 10.182.56.79 with HTTP; Wed, 4 Jan 2017 23:06:36 -0800 (PST) In-Reply-To: References: <71d822e413ac457a530e1c367811cc24@cock.lu> <77b6dd25-0603-a0bd-6a9e-38098e5cb19d@jonasschnelli.ch> <74aeb4760316b59a3db56c0d16d11f28@cock.lu> From: Chris Priest Date: Wed, 4 Jan 2017 23:06:36 -0800 X-Google-Sender-Auth: LMC1o3MQL6nvOOWh06chCVQty6Y Message-ID: To: Jonas Schnelli , Bitcoin Protocol Discussion Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, FREEMAIL_FROM, 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 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:06:39 -0000 On 1/3/17, Jonas Schnelli via bitcoin-dev wrote: > > There are plenty, more sane options. If you can't run your own full-node > as a merchant (trivial), maybe co-use a wallet-service with centralized > verification (maybe use two of them), I guess Copay would be one of > those wallets (as an example). Use them in watch-only mode. 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. If more people mined, this method will not work as well because it would require you to call the API of hundreds of different potential block creators.