i have been busy last 6 months , i had staking running on AWS and now my wallets will not work. I looked up the new patch and it has a auto load and build wallet. how do i load my seed? did we hard fork and have i lost my wallets?
Delete the blockchain from your environment, located in C:\Users\username\AppData\Local\Dcrd\data\mainnet (Windows), or in ~/.dcrd/data/mainnet (Linux, I believe). Download the latest version (8.2 as of now), and start dcrd. Let it download the entire blockchain before moving on. Recreate your wallet using your seed. There was a release some time ago, I think it was between 0.5.0 and 0.6.0 that required users to redownload the blockchain. I don't think this caused the issue, but I wanted to mention it. Also - it's kind of difficult to assist when your problem description is "it doesn't work". Give my suggestion a try though and it should fix any issues you have.
As long as you still have your seed saved your best bet is probably to set everything up from scratch following this guide: https://docs.decred.org/getting-started/beginner-guide/ Using dcrinstall makes it very easy.
Thank you jvc. I will try the guide, also is tire way to run more then one wallet and a Linux box to reinstall mulitibul seeds?
Yes, but the setup gets somewhat complicated. I haven't setup my second wallet instance in a config file yet, so the commands get a bit sloppy. In my code examples, capitals are for you to fill in with your existing settings, and I'm assuming you are not using config files. In addition, nothing with your primary wallet will change. You will still interact with your primary wallet using the same commands you use now. First off, create a new directory and copy dcrctl and dcrwallet to the new directory. This should be separate from your main Decred folder. Dcrd should stay in your main Decred folder. Restart your dcrd so it listens to an additional port. We will be setting up the 2nd wallet to use this port instead of the default port. Code: ./dcrd /rpclisten :9109 /rpclisten :64123 /rpcuser USERNAME /rpcpass PASSWORD Start dcrwallet with a different directory than the default directory, point it to dcrd's new port you opened above, open an additional port for dcrwallet to interact with dcrctl on, and create the wallet. Note: I haven't set this up on Linux so the directory syntax in the example below might be screwed up. Code: ./dcrwallet /A ~/YOURNEWWALLETDIR /c 127.0.0.1:64123 /username PASSWORD /password PASSWORD /rpclisten :64124 --create I ran into certificate issues and the only way I could get around them was to copy the rpc.cert and rpc.key files from the hidden dcrd directory to the new directory. I believe this is in ~/.dcrd/. Copy both rpc files to ~/yournewwalletdir/ Every time you need to interface with your secondary wallet, you have to specify the rpcserver by port and the location of the rpc cert file. This is where it gets sloppy as I haven't set this up in a config file yet. For example, to check the balance of the secondary wallet: Code: ./dcrctl /rpcuser USERNAME /rpcpass PASSWORD /rpcserver 127.0.0.1:64124 /rpccert ~/YOURNEWWALLETDIR/rpc.cert --wallet getbalance Hopefully this gets you up and running. I'm not sure if there's another way to set this up as I haven't played around with it too much, but I feel that it's pretty sloppy. It does work though, and maybe I just need to setup .conf files for the second wallet to clean things up a bit.
I like using a seperate config file for multiple dcrwallets on one box. For example, on my linux box I have: Code: jcv@triforce ~ $ ls .dcrwallet .dcrwallet/ .dcrwallet2/ .dcrwallet3/ .dcrwallet-main/ Then I start the wallet with: Code: dcrwallet -C ~/.dcrwallet2/dcrwallet.conf In each of the config files I specify at least: Code: appdata=/home/jcv/.dcrwallet2/ rpclisten=127.0.0.1:SOMEUNIQUEPORT
Ok i have been abel to load the seed to the web wallet and see o.ooo dcr i had tickets at the time the shut down. i cant see any tickets or tell if they will return a refund from not voting. have i lost my tickets and the dcr i paid for the tick's?
Using the web wallet with a seed that was buying tickets does not work well. Best to stick with Decrediton, Paymetheus, or the CLI tools. You have definitely not lost your DCR.
so at least i know my seed is good i can see transactions.. i should reload seed on my linux box and add seeds to one wallet?
I'd suggest loading the CLI tools on your linux box and checking what they say. Can't go wrong with the CLI tools.
There are updates to the webwallet in the works but it is still unlikely it will ever really do staking so for that, cli or gui wallets are the way to go.
Ok genitalmen, its been a minute working on this becuse of life... i now have wallett ctl all updated and seed inported.. getbalance returns : "balances": [ { "accountname": "default", "immaturecoinbaserewards": 0, "immaturestakegeneration": 45.994296, "lockedbytickets": 2.05, "spendable": 74.95, "total": 122.944296, "votingauthority": 2.05 }, this PoS has been down at least 6 months when will i have acsees to all the dcr under spendable?
When i try to send i get... ~/decred $ ./dcrctl --wallet sendtoaddress DsbRZnjowSLyeV7R2kKNhLQYgvL1tdhFKqd 70 -32603: -32603: orphan transaction 8de315a5f3cabd2da65c99816f5b87bd460338b04d403a8d96eabb65d6e4e6e1 references outputs of unknown or fully-spent transaction bb22486f58047f6eb1e7c11bc0404a0e2503267a0bcd073fbb018afbf5702bd9
Are you saying that ticket is from 6 months ago and your wallet has been offline that whole time? Is dcrd on the lastest block? If so, try starting wallet with "dcrwallet -enablevoting" and then unlock wallet, and "dcrctl --wallet rebroadcastmissed"
Yes to question 1... yes to blockchain is now updated your instructions returned : Revoked missed ticket XXXXX>>>> and Inserting unconfirmed transaction. and getbalance lockedbytickest is now 0 "accountname": "default", "immaturecoinbaserewards": 0, "immaturestakegeneration": 47.994048, "lockedbytickets": 0, "spendable": 74.95, "total": 122.944048, "votingauthority": 0 }, sendtoaddress returns: orphan transaction 56a5af7c9cd429275a53743620920628c98e2bf6d30c7e20791e88f095350c2a references outputs of unknown or fully-spent transaction bb22486f58047f6eb1e7c11bc0404a0e2503267a0bcd073fbb018afbf5702bd9 Thank you!
You need to wait for 256 blocks to see if that clears the immature to spendable. If you still cannot spend after that, you may need to reseed the wallet and/or redownload the blockchain. Are you using the latest version?
spendable is starting to change! ill give a day or so.. "balances": [ { "accountname": "default", "immaturecoinbaserewards": 0, "immaturestakegeneration": 33.995784, "lockedbytickets": 0, "spendable": 88.948264, "total": 122.944048, "votingauthority": 0
so i have now .. getbalance: "balances": [ { "accountname": "default", "immaturecoinbaserewards": 0, "immaturestakegeneration": 0, "lockedbytickets": 0, "spendable": 122.944048, "total": 122.944048, "votingauthority": 0 }, add sendto returns : -32603: -32603: orphan transaction f783c1da61b4bbea62d935198b58192954a3e4ead0781d2ae58df939b67c1be0 references outputs of unknown or fully-spent transaction f05a7389d44505cacfb147e288a5daeb3fb9a1657ef21c79d03460671e544c30
I checked on slack and they said to reseed. I know you have already done that. Try dcrctl --wallet consolidate inputs ("account") and/or sending a small amount of DCR (maybe 1) and see if that works. You could try to reseed again after completing some of the earlier commands.