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 14B47D61 for ; Wed, 11 Apr 2018 05:21:35 +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 7DE0417E for ; Wed, 11 Apr 2018 05:21:34 +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 1C5B014C0B9 for ; Wed, 11 Apr 2018 14:21:33 +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:21:33 +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 13DA04C079 for ; Wed, 11 Apr 2018 14:21:33 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw21.oz.hdemail.jp (ip-10-172-131-196.ap-northeast-1.compute.internal [10.172.131.196]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id 1239B14C0B9 for ; Wed, 11 Apr 2018 14:21:33 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qt0-f199.google.com (lb07.oz.hdemail.jp [54.238.57.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw21.oz.hdemail.jp (Postfix) with ESMTP id AC48B148C111 for ; Wed, 11 Apr 2018 14:21:32 +0900 (JST) X-Received: by mail-qt0-f199.google.com with SMTP id f13so502157qtg.15 for ; Tue, 10 Apr 2018 22:21:32 -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=7dS6fxAVxf8ErsgoceWYIStpNZmVzO2/qp8VHZ0fY+4=; b=myKgVNT2nQtiQSn9OT4FXSmoKjQyRWFlFaibiFMHn+eReZQO4nyMphQGL89U7nAzp/ ogS/2SnxpfOHT9imEclctW7x6eZvGxYGUhQ7eIEVU8it9DFt6qFSmW96AZkb61ZGypXq b1k6hWL4ySeg2aTP5kxR0ac+ydrgYkfBRsB1SnlC+rKDTzpuRhjsb7JacVUH63tSsKOl Fs1HxC/EKOxrgTV8xKzl5FOeiCUOcEGv7cZP5HooCFWGiIe7a8BJAbnnXq0s2TPjxHPQ 2mTmwYMN8iPXmlddXD4cxbWv+JyyDKrZmuAgaVNqq4EaEqSdJSdtm9O+b7ezFfzMXDWB b9Kw== X-Gm-Message-State: ALQs6tAHKWnR8FMHhYPsygkO0dTjDjU5C0mMUW1uqwnBqO58Ec6cY6tw tkxRSYws/4KNqJ2zGAyys5vO1U/FiS2x5FXjtWgs7vjnp4DoNlPGsg6RsYdL452DLVkU897T6l/ YbllWtBzcaFntE8zcHvQJw9IVgU0raYqK0TCUxqfzsT7DSc46WBuHCOOiHgeltGIOTf4/Polnp5 ZXjhhRhLYHeKNlDd+SooA5xLjAtQv1x2EEyKTR2U2hknRA6GLtDbsITdu2qHe7j4OBi1RaShP/l zX5S9bUOXMfKYrBN2c9xAM19Q5cIcqY8t9ZO+x1Mo6pRt/jSk2yMembLqbhB+yJv86S2torItnN fftIzXzfrTbJ9ZZ8aqhyoRRySKA= X-Received: by 10.200.66.80 with SMTP id r16mr5175969qtm.289.1523424091307; Tue, 10 Apr 2018 22:21:31 -0700 (PDT) X-Google-Smtp-Source: AIpwx49VKiPH9aANhyLkAxAiK5Y03TAoOxfkgkh0lskw6Q3uVXw1x9qxBv/zhUQmvmtXSssRMka5AHowME2UXLMFeco= X-Received: by 10.200.66.80 with SMTP id r16mr5175950qtm.289.1523424091037; Tue, 10 Apr 2018 22:21:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.12.208.26 with HTTP; Tue, 10 Apr 2018 22:21:10 -0700 (PDT) In-Reply-To: References: From: Karl-Johan Alm Date: Wed, 11 Apr 2018 14:21:10 +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:21:35 -0000 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. > 2. When does confirmations can be -1 ( conflicted )? > What does it mean to have conflicted transaction? > Is it about Transaction Malleability? Double Spend? or both? A transaction is conflicted if a different transaction exists that spends the same inputs. A transaction gets -N confirmations if it is mined in a block, and that block is orphaned away, and a different transaction is mined in the new block so that the transaction becomes a double spend.