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 2A601E2F for ; Tue, 10 Apr 2018 20:29:27 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wr0-f194.google.com (mail-wr0-f194.google.com [209.85.128.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5265825A for ; Tue, 10 Apr 2018 20:29:26 +0000 (UTC) Received: by mail-wr0-f194.google.com with SMTP id c24so14048442wrc.6 for ; Tue, 10 Apr 2018 13:29:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Q04H1TVw1aWgQcD/3aSgHhPiNBvRJKSRzNZKn7U25io=; b=VZgiJ2VlODa/24MutzIjs4UzNHh6Eaqm9pHjiKgV5c9n2Of7sCCmWaTX728J3TOxwj MmmjqZigAcGLgqlkyuvmQi5trNriz19WcQg7QIqIQwSKAllWVkUXeUIE1EP+3iuVhv2d ZXPLBWYxUS5Bm/dZxIUpntLjkpvrRuYS2Bz+LvcH7bLEO1XNN7kUwrM9K8hyMQe5h/0e 8FxsAOt8xJrpF194lXnL4iW8JNEt32LbZ8wpen0nL/I8Bsus1dskhFlRGhxosxKq/luP JRWmR9SGCiVPqY0V6uZ1Ya6H3A4N3p9zpRghRnWmNj1UEPPZmn+DsGxgNqhYfKOFVqwk iNTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Q04H1TVw1aWgQcD/3aSgHhPiNBvRJKSRzNZKn7U25io=; b=Pmb2GP6Em9ArkbwQlSths2pkrmOUKFlhCJvXGQZHsEnes1evG8nGFS/QEujeIkjiJI ADh5K2xQHedBBugCiVlgO1/9weDl7XeWXwDjZ4b0t2dBNPFJlunuA3mSKOpIp3aZ2MDO KMzjM+rYdq7Vrqn6Qb4o4LDJQLbW8Vy9mrCpGFM4p4Qk6wr3lhgB02Xhj/dZXbKxcz7Z X1Vk5pd0uzO6jiGP+H3QDYYwl5+ZOFsgZAbR9XRCuuMAdRK41f3fVo+brld2dDvJOL+j 3KxEZAAkt1FogA+jL73cQbcg27D5uXHy/D7Zh34nr8+Wb//bHGyiJ9ipYuYqctbc9zNe Jf7g== X-Gm-Message-State: ALQs6tAGu2j4R6lzKVqiJ/jKWzjQKShmUYCrZ47xE2pkT7tidl+ijJ4A qUsEITGcGsUXdazZQgoILiStIPbqg7Ypee5sI7T2kaEl X-Google-Smtp-Source: AIpwx4+ZJ4i6Ff0F9xDZNB9meRx5xzxTltXbIw41B4iuA8wTCbdivzF957OYSQNS86X17jz4eE6UeTMPzq4cbsJVcc4= X-Received: by 10.223.133.139 with SMTP id 11mr1472350wrt.28.1523392163678; Tue, 10 Apr 2018 13:29:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.152.83 with HTTP; Tue, 10 Apr 2018 13:29:23 -0700 (PDT) From: Maksim Solovjov Date: Tue, 10 Apr 2018 23:29:23 +0300 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="001a1146bb18c50fb4056984609c" X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, 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 X-Mailman-Approved-At: Tue, 10 Apr 2018 20:33:52 +0000 Subject: [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: Tue, 10 Apr 2018 20:29:27 -0000 --001a1146bb18c50fb4056984609c Content-Type: text/plain; charset="UTF-8" Hi, I have few questions regarding ListTransaction RPC call and I hope you can help me. Documentation for the RPC call is here: https://bitcoin.org/en/developer-reference#listtransactions 1. What does it mean for a transaction ( with 0 confirmations ) to be *trusted* or not? There is such field in the response of ListTransaction As far as I know bitcoin - nothing is trusted unless there are some numbers of confirmations. How does this value is set to true or false? 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? 3. *walletconflicts*. What if I add watch-only address to my bitcoind process. This address will not be a part of my wallet. Now, someone will pay me to this address and someone else will make Transaction Malleability ( for the sake of example, lets assume this second one will be confirmed, not the original one ). Will I get a first transaction in *walletconflicts* array when ListTransaction will return me second transaction in the response? Thank you in advance! --001a1146bb18c50fb4056984609c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I have few questions regarding List= Transaction RPC call and I hope you can help me.
Documentation fo= r the RPC call is here:

1. What does it mean for a= transaction ( with 0 confirmations ) to be trusted or not?
There is such field in the response of ListTransaction
As far a= s I know bitcoin - nothing is trusted unless there are some numbers of conf= irmations.
How does this value is set to true or false?

2. When does confirmations can be -1 ( conflicted )?=
What does it mean to have conflicted transaction?
Is i= t about Transaction Malleability? Double Spend? or both?

3. walletconflicts. What if I add watch-only address to my bi= tcoind process.
This address will not be a part of my wallet.
Now, someone will pay me to this address and someone else will make = Transaction Malleability ( for the sake of example, lets assume this second= one will be confirmed, not the original one ).
Will I get a firs= t transaction in walletconflicts array when ListTransaction will ret= urn me second transaction in the response?

Thank y= ou in advance!
--001a1146bb18c50fb4056984609c--