Hi, these are my tickets (still immature apparently): a6117cf1ce9b1a9e13b289b1cb46947ebbb5e78cbcd44a9b85da89c5e30b780b 36a7ff266f8581fbb7ef099e01f659740183394833d672fb7e64c139b2258415 0df4d16cf655f1e9cb540ff5f08d49848ffd904e5af7d8f519b6dc2968f2b334 e302ce319919396ec836b4702b32001f5c94a08ebf2f3254eb8b73638a0e7447 5a6b1079aeff4f7694ce1b45ff7f63eaacd54bf6618a0c7af03742b33f46af58 bcb3fc6be58d2edfd9cc23c42e459affa11fd946e9fc2428f3d1f602a295d460 080cc20975fad1f01383afa3d5a7fc8060a72cbfb46a38cca0efc2c0345cdc6a d9e1f514a61ceee896d718f7682774379c8865ad668bdd17216a0188b3d5dd9d 25c43048afa405af4d3ef7c2f87edacca865cd964508b83033ab3f6da76a79b7 d478f38fdd75ba76fb57f3608ef27d7d5ef69b486a63625bdc6007a1509bc9c6 612552cd8086f903899dafc51905fe9b11c117214b545c6406954ca53fe5e4c9 7fde69be19510ba9e91ab4422a1ba98a0609be52cc63475235725d73a34469da 32bda83ad1143bbdadbc2d1132a265e4b3b28c8ce9a79e2d0bf35865880bdbfa The oldest is from 2016-02-08 and the newest from 2016-05-31. All of the tickets have the same '{"votebits": 1, "votebitsext": "03000000"}'. I upgraded to v0.7.0, tried to rescan my wallet, recreated a new wallet from the same seed - funds still locked. Are there some commands that extend ticket expiry? I might have called rebroadcastmissed, rebroadcastwinners, missedtickets or some others. Is there someone here who can help me understand what is going on? Thx P.S.: I have never been a part of any pool mining.
I just confirmed that none of those tickets are live (which is expected based on how old they are). I also checked the first two and can see they were indeed missed (you never voted on them). Code: $ dcrctl missedtickets | grep a6117cf1ce9b1a9e13b289b1cb46947ebbb5e78cbcd44a9b85da89c5e30b780b "a6117cf1ce9b1a9e13b289b1cb46947ebbb5e78cbcd44a9b85da89c5e30b780b", $ dcrctl missedtickets | grep 36a7ff266f8581fbb7ef099e01f659740183394833d672fb7e64c139b2258415 "36a7ff266f8581fbb7ef099e01f659740183394833d672fb7e64c139b2258415", So, with that we know that the missed tickets will need to be revoked. An easy way to check if they have been revoked is to look at the commitment address of the original ticket to see if there is a revocation associated with it. In the case of a6117cf1ce9b1a9e13b289b1cb46947ebbb5e78cbcd44a9b85da89c5e30b780b, we can see the commitment address is DsnYpoBxZXekzoZxDN6kHPRd7Sukqgczirp and that it does not have a revocation associated with it. So, in order to make sure those are revoked, you'll want to do the following: Ensure your wallet is unlocked because it can't create the revocation transactions if it is locked Issue a rebroadcastmissed notification so wallet rechecks all of the missed tickets and issues the revocation (NOTE: This is typically done by the wallet for you periodically so long as it's unlocked, but we're doing it manually here so you can see it happen). Code: dcrctl --wallet rebroadcastmissed You should see log messages about it issuing revocations. You also should see the revocation transactions show up underneath the aforementioned commitment addresses via the block explorer. Once the revocation is mined into a block, wait 256 blocks for the coinbase maturity to be reached and your coins will be available again.
my walletinfo says: Code: { "daemonconnected": true, "unlocked": true, "txfee": 0.01, "ticketfee": 0.01, "ticketmaxprice": 0, "balancetomaintain": 0, "stakemining": false } I issued rebroadcastmissed and the terminal seemed fine (no errors or anything) but nothing in wallet/dcrd logs. The only lines I see in my wallet logs are 'Connecting block' which seems to happen whenever a new block is mined. Should I somehow increase the verbosity of the logging output? You can guess my funds are still locked. I don't believe I could be on a forked chain as I'm in sync with https://mainnet.decred.org/ - both always seem to have the same last block. @davecgh do you have any pointers from here on and thanks for trying to help btw!
What version did you upgrade from? It might be worth while to delete and redownload the blockchain. This will take some time, of course.
I went from 0.4.0 to 0.7.0 but I have a feeling it had been broken before that. Anyway that was the last thing I can think of as well.
I re-download the chain and created a new wallet file (same seed). This time my wallet actually made all necessary revocations which are currently all at 139 confirmations. So, when those reach 256 my funds should all be unlocked - nothing else to do, right?
Great. Glad to hear recreating from seed resolved it. I also checked and see the revocations associated with the commitment addresses. Correct, the funds will mature and be available for spending once they reach 256 confirmations.
I have a problem with unlocking my funds. I have tryed Code: ./dcrctl --wallet rebroadcastmissed but it doesn't do anything. There is no log that I did anything. Does anyone have any other idea? I have deleted all the dcr maps and recreated my wallet and everything. Wallet has been unlocked for 3 days and I run that line 3 days ago.
Can you provide more information? Are you sure that you actually have missed/revoked tickets? What version of dcrwallet are you running?
So I'm running the latest one 0.7.0. Well when. I check how much funds I have it says some number and when I check locked it says that there is locked over 200 and spend able is the rest. So that is why I know it has to be somewhere. I don't have any tickets.