Tx Not Confirmed For Hours

Discussion in 'Transactions' started by tunnus, Mar 21, 2016.

  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    any idea why this ticket purchasing tx does not get confirmed for hours?
    354738d85fe4a24110be806048c5f57785b6a54828d54e4aca7f50d773e76d43
     
  2. David

    David Sr. Member

    Jan 22, 2016
    364
    207
    Male
    USA
    Not sure... everything looks normal to me. It was confirmed shortly after you posted here in the forum. It was unconfirmed for hours prior to your post?
     
  3. kaida

    kaida New Member

    Jan 4, 2016
    78
    24
    Information Security
    San Francisco, CA
    Your ticket was in the mempool waiting to get put into a block. Your ticket was included in block 12415. If you look at the block explorer, there were hundreds of other tickets in the mempool at the time based on the fact that each block starting 12382 all the way through 12427 were at the max 20 tickets per block. If you wanted the ticket to get put into a block sooner, increase your fee so miners have incentive to pick your ticket over others.
     
  4. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    right, that must be the reason. I didn't know about that maximum. Thanks!

    Now that I restarted the deamon it tries to double-spend that transaction though - as if it didn't see that it got confirmed:

    09:17:56 2016-03-22 [WRN] WLLT: A chainSvr error was returned attempting to purchase a ticket; ticket purchases aborted.
    09:18:23 2016-03-22 [INF] WLLT: Connecting block 000000000000263631b6f17cb11829137fb9f118be33c988e0d56d930f20fcaf, height 12531
    09:18:23 2016-03-22 [WRN] WLLT: Failed to send raw transaction: -22: TX rejected: transaction 6726c038717804b20a65b7fcbd0846caed04602c1e21d88627413773eb3fcc49 tried to double spend coins from transaction 35fde9deb76914c3655668104ee8558f813bdebaae65993bf197cc756325e543
    09:18:23 2016-03-22 [WRN] WLLT: A chainSvr error was returned attempting to purchase a ticket; ticket purchases aborted.

    and this happens after it receives every new block.

    Maybe I need to somehow flash all the wallet / daemon data (except for the private keys) ?
     
  5. Ayush

    Ayush Full Member
    Advocate (Facebook)

    Jan 9, 2016
    512
    100
    Male
    .
    .

    Hi first are u on v0.0.8?
    If yes and still face the problem, recreate wallet from seed after deleting dcrd and dcrwallet folder in app data.Thats how I fixed my problem
    If u need any assistance ask me
     
  6. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    I tried deleting everything except wallet.db
    Redownloaded the blockchain, and for some reason my balance was some 8DCR less than before. No doublespend attempts by the wallet anymore though (just not enough to buy a ticket, lol )

    Then I saw your remark about 0.0.8, upgraded (from 0.0.7) and did the deletion thing again. Now my balance has decreased by 200DCR more.

    ok I suppose I should try really deleting everything and restoring the wallet from the seed. Not fun, but well...
     
  7. tacotime

    tacotime Hero Member

    Dec 7, 2015
    410
    1,133
    Please make sure you backup your wallet first. Allow dcrd to sync up first. Then restore your wallet from seed using the v0.0.8 release.
     
  8. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    #8 tunnus, Mar 22, 2016
    Last edited: Mar 22, 2016
    ok I did that. Deleted everything and restored the wallet from the seed. Now I get 0 balance! I know the wallet seed was entered correctly, because it gave me the same hash (I saved it).

    I'm a bit confused because I can't figure out what I did wrong.

    The only thing is that didn't wait for dcrd to finish syncing first, but restored the wallet and ran it while daemon was still catching up. That shouldn't really matter, should it?

    I'm not worried for my coins, I'm sure they are waiting for me in the blockchain - but at the moment I can't figure out what to do. Also, I have a backup of the wallet file from the previous installation, as well .cert files.

    Edit: apparently, waiting for the daemon to sync first was important. Now I deleted the wallet but not the blockchain, restored the wallet from seed, and the result is different again - I get some balance, but much less than it shoud be.
    (checking with the command --wallet getbalance "default" 0 all )

    I noticed something though: the wallet says "rescan for 60 addresses" whereas before it was saying "rescan for 65 addresses" . Now I'm thinking that may be the problem. All the addresses should be from the same seed anyway, so I suppose I should just generate 5 more and retry.

    Edit2: nope, didn't help. Now it says "rescan for 200 addresses" and the balance is the same. Could there be some specific branches that are created differently? For example, I remember I generated some address to mine on the pool, and may be that one was not just "getnewaddress". I don't remember what was the command though.
     
  9. tacotime

    tacotime Hero Member

    Dec 7, 2015
    410
    1,133
    Allow dcrd to sync up completely before you connect a seed-restored wallet to it. What are the results when you do that?
     
  10. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    (sorry for repost- I added this to my post above before noticing the reply)
    apparently, waiting for the daemon to sync first was important. Now I deleted the wallet but not the blockchain, restored the wallet from seed, and the result is different again - I get some balance, but much less than it shoud be.
    (checking with the command --wallet getbalance "default" 0 all )

    I noticed something though: the wallet says "rescan for 60 addresses" whereas before it was saying "rescan for 65 addresses" . Now I'm thinking that may be the problem. All the addresses should be from the same seed anyway, so I suppose I should just generate 5 more and retry.

    Edit2: nope, didn't help. Now it says "rescan for 200 addresses" and the balance is the same. Could there be some specific branches of the address tree that are created differently, not just with getnewaddress command? For example, I remember I generated some address to mine on the pool, and may be that one was not just "getnewaddress". I don't remember what was the command though.
     
  11. tacotime

    tacotime Hero Member

    Dec 7, 2015
    410
    1,133
    Ah, you need to run:
    Code:
    dcrctl --wallet getbalance '*' 0 'all'
     
  12. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    same result
     
  13. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1
    another thing I noticed that each time I run the wallet it does the rescan not from the beginning, but from the previous highest block. So for the new addresses I generated it actually didn't do a rescan. How can I force it to do a full rescan?
     
  14. Shadowlance

    Shadowlance Full Member

    Jan 9, 2016
    220
    155
    Male
    I think you'll have to get rid of wallet.db. I'm pretty sure that's where it stores that info. Just rename it or move it then rebuild from seed again.
     
  15. tunnus

    tunnus New Member

    Mar 10, 2016
    12
    1

Share This Page