Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8B653CE0 for ; Wed, 11 Apr 2018 05:23:07 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C40641A0 for ; Wed, 11 Apr 2018 05:23:06 +0000 (UTC) Received: from ip-10-217-1-36.ap-northeast-1.compute.internal (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id BCD5014C0B9 for ; Wed, 11 Apr 2018 14:23:05 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1) by 0 with SMTP; 11 Apr 2018 14:23:05 +0900 X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id 0ACAB4C07A for ; Wed, 11 Apr 2018 14:23:05 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw29.oz.hdemail.jp (ip-10-166-152-121.ap-northeast-1.compute.internal [10.166.152.121]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id E027014C0B9 for ; Wed, 11 Apr 2018 14:23:04 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qt0-f198.google.com (lb06.oz.hdemail.jp [54.238.50.28]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw29.oz.hdemail.jp (Postfix) with ESMTP id 7E38C148C101 for ; Wed, 11 Apr 2018 14:23:04 +0900 (JST) X-Received: by mail-qt0-f198.google.com with SMTP id x13so512429qtf.6 for ; Tue, 10 Apr 2018 22:23:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=m+t7LVVKQ8I9iFIDYiZAxmIZ8b2xtTyaV+d6mGkPk+Q=; b=jKRhvCaFNA/PFmljAwrexH5gNv8IpwIWSQR+JcvPLAnFAiVw6Y/3kur00Q9YOEgj2I lmOWH1+hvGP1Bmt5purjLliRt8rfkvrQnz+l/shq489c4ba4o6f5ttHRoaVLnJXiI0O5 s0COdw5odgYITK0ob6IIkyUI3dgL8trOuIAV1B4TPW/lnde1YRmfHBcqVTHlYzSPlmYK xPbNB/mBHRhj+ZhqtATDJ+NtP6l5FjM6bvtmSh6rC+gtwmlE1NeboWFBzzuy12Q5m8gj B+eT6oUZW4oMTaNhg+mwU/7oi9q8t7AXQxUUHLxBbCnVbQRpA04Ya8Y+CleaedLQXDaC bmyA== X-Gm-Message-State: ALQs6tDgq4rh8rSbcJ6KTSEM99B/BfqwoQCNhpo8tc7/8AWWmFhZP2Hy Ptor2T9vTHA7h7WFmSxCA2NSa4WCw7dhWk+nyJ4e8C7IHcORELvhI7glzb9D4O1xAhkkori8JKu 3tTJVm0e8jDJjZd7y4T3Dt7BkCRlUvs2bl/H3s8VItKKNwAog6wz6043JTSybf7R3zFej40ruRE KBrHE55KLZIqDSKfQnlR5btzAhPRKhGlUCWwwuDqpbK3NhsgTQDY6Lq0iC7Opzghs3Sj9fGP63S GRaFmJj025Cwhn21mIrgg2f9Ivz1JFKGNPGJj6CshMlPdcmUBo9YTPswsVPcVZ5q9JS/kICB3BV BXwtpNoWBgZWYX+ZwdpFZXzxTuU= X-Received: by 10.200.114.83 with SMTP id l19mr5197589qtp.325.1523424183023; Tue, 10 Apr 2018 22:23:03 -0700 (PDT) X-Google-Smtp-Source: AIpwx49P0o6YVKCCLDe/4OPvaQrXQyTiJmYXX3ecNqQBcz1JeRZO8JljhMYQOWWQiCwsn4I3FF+7OojVK1VUExftzVg= X-Received: by 10.200.114.83 with SMTP id l19mr5197576qtp.325.1523424182802; Tue, 10 Apr 2018 22:23:02 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.12.208.26 with HTTP; Tue, 10 Apr 2018 22:22:42 -0700 (PDT) In-Reply-To: References: From: Karl-Johan Alm Date: Wed, 11 Apr 2018 14:22:42 +0900 Message-ID: To: Maksim Solovjov , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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] Few questions regarding ListTransaction 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: Wed, 11 Apr 2018 05:23:07 -0000 Clarification on one part below: On Wed, Apr 11, 2018 at 2:21 PM, Karl-Johan Alm wrote: > On Wed, Apr 11, 2018 at 5:29 AM, Maksim Solovjov via bitcoin-dev > wrote: >> 1. What does it mean for a transaction ( with 0 confirmations ) to be >> trusted or not? > > It is trusted if (1) it is final (i.e. it can't be replaced), (2) it > is not in a block that was reorged out (negative confirmation count), > (3) the 'spend zero conf change' option is set, (4) it is in the > mempool, and (5) all inputs are from us. "can't be replaced" here means it cannot be replaced through conventional means. It is always possible to replace a transaction that has not yet been confirmed, e.g. by asking a miner to mine a conflicting transaction directly.