Bitcoin Forum
May 03, 2024, 09:25:30 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Weird data on multisig address in bitcoind. A bug?  (Read 1115 times)
Sword Smith (OP)
Sr. Member
****
Offline Offline

Activity: 406
Merit: 286


Neptune, Scalable Privacy


View Profile WWW
July 10, 2014, 05:42:05 PM
Last edit: July 10, 2014, 06:03:28 PM by Sword Smith
 #1

When I use the command "listsinceblock" in bitcoind I get some weird looking data for a multisig address. Can anybody explain this to me? Lookng at the txid, we can see that the two listed transactions represent the same transaction. Is this a bug in Bitcoin Core? The list for single signature addresses look correct.


The multisig address should only have one incoming transaction and no outgoing transactions as can be seen on blockchain.info:
https://blockchain.info/address/34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw



Code:
sirius@sirius-ThinkPad-Edge-E540 ~/Documents/bitcoin-0.9.2.1-linux/bin/64 $ ./bitcoind listsinceblock
{
    "transactions" : [
{
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "send",
            "amount" : -0.00990000,
            "fee" : -0.00010000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
        },
        {
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "receive",
            "amount" : 0.00990000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
        },


1714771530
Hero Member
*
Offline Offline

Posts: 1714771530

View Profile Personal Message (Offline)

Ignore
1714771530
Reply with quote  #2

1714771530
Report to moderator
1714771530
Hero Member
*
Offline Offline

Posts: 1714771530

View Profile Personal Message (Offline)

Ignore
1714771530
Reply with quote  #2

1714771530
Report to moderator
1714771530
Hero Member
*
Offline Offline

Posts: 1714771530

View Profile Personal Message (Offline)

Ignore
1714771530
Reply with quote  #2

1714771530
Report to moderator
"In a nutshell, the network works like a distributed timestamp server, stamping the first transaction to spend a coin. It takes advantage of the nature of information being easy to spread but hard to stifle." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714771530
Hero Member
*
Offline Offline

Posts: 1714771530

View Profile Personal Message (Offline)

Ignore
1714771530
Reply with quote  #2

1714771530
Report to moderator
bitsta
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500


r00t-dev


View Profile
July 28, 2014, 12:23:32 AM
 #2

When I use the command "listsinceblock" in bitcoind I get some weird looking data for a multisig address. Can anybody explain this to me? Lookng at the txid, we can see that the two listed transactions represent the same transaction. Is this a bug in Bitcoin Core? The list for single signature addresses look correct.


The multisig address should only have one incoming transaction and no outgoing transactions as can be seen on blockchain.info:
https://blockchain.info/address/34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw



Code:
sirius@sirius-ThinkPad-Edge-E540 ~/Documents/bitcoin-0.9.2.1-linux/bin/64 $ ./bitcoind listsinceblock
{
    "transactions" : [
{
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "send",
            "amount" : -0.00990000,
            "fee" : -0.00010000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
        },
        {
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "receive",
            "amount" : 0.00990000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
        },


please try to use it with proper parameters/arguments.

Code:
listsinceblock [blockhash] [target-confirmations] 
example: ./bitcoind -listsinceblock 0000000000000000365692b410bf843d6f7b7e0959c064f959776114e908fa8d

(this should list your tx as it s the previous block before your tx was made)


taken from the API list:
Quote
API description of "listsinceblock [blockhash] [target-confirmations]": Get all transactions in blocks since block [blockhash], or all transactions if omitted. [target-confirmations] intentionally does not affect the list of returned transactions, but only affects the returned "lastblock" value.
DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4615



View Profile
July 28, 2014, 05:02:56 PM
 #3

I don't use listsinceblock much, so perhaps I'm misunderstanding what I'm looking at.  It doesn't look like there's anything wrong to me.

As far as I can tell, you sent from the wallet back into the same wallet, and you are seeing both sides of that transaction, right?

Code:
{
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "send",
            "amount" : -0.00990000,
            "fee" : -0.00010000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
 },

This appears to be an indication that a total of 0.0099 + (0.0001 fee) = 0.01 BTC was sent from the wallet to an address of 34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw.  I assume that this is because you created a transaction spending the following 0.01 BTC output from this wallet and paying a 0.0001 BTC transaction fee:

Code:
"txid" : "e68f95873e41613d6610d43a2fd9919772fccce521fd7041ca14fd0da8627c09"
"vout" : "27"

Meanwhile . . .

Code:
{
            "account" : "",
            "address" : "34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw",
            "category" : "receive",
            "amount" : 0.00990000,
            "confirmations" : 13,
            "blockhash" : "0000000000000000064594fd44816f8ab656d2f2627848990c47f791e4276ad4",
            "blockindex" : 131,
            "blocktime" : 1405007016,
            "txid" : "7850528d3b57e3993d56b4f7cd90198fe3a329a4045bb240737758c6fb554b94",
            "walletconflicts" : [
            ],
            "time" : 1405006463,
            "timereceived" : 1405006463
},

This appears to be an indication that a total of 0.0099 was received in the wallet at an address of 34N5MSC3brnr183yRBBQYFRYNVmGf1ymhw.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!