Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
listsinceblock incorrectly showing some conflicted transactions #10656
Comments
fanquake
added the
RPC/REST/ZMQ
label
Jun 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RHavar commentedJun 23, 2017
Normally when a transaction is conflicted, listsinceblock will show it as having negative confirmations, representing how long ago it conflicted. However, looking at the results of my listsinceblock shows dozens of conflicted transactions with 0 confirmations (as well as transactions whos parents have long been forgotten by the network).
An example:
Which would make you think it's a pending receive, so lets dive deeper:
Decoding that, you'll see it's sourcing:
{ "txid": "6cc33df2c5730a6f4689a0017f6ee7d6e56edee89f5d1c47bc4accefca0a5c97", "vout": 0 }Which is a transaction that has not confirmed, nor in my nodes mempool. Fortunately we can find it on tradeblock, and see it's conflicted with dd0ab2618d4df044d369b56ce96f6f8d9dca6e04f4c180fa73e8ace20b3653e3 which has long confirmed.
So this means that our original transaction is just sitting in listsinceblock is actually conflicted and impossible to ever confirm, yet not marked as such.