I know some people have set up redundant wallets for PoS in case one goes down, but I haven't seen any guides. It's something I think should be part of the official docs. Would anyone mind giving a short how-to on how it's done? Just the instructions will be fine, I can pretty it up. You will be acknowledged in the docs along with all the other guide authors.
I'm not sure if that's what they're called. It's a slave wallet that responds to votes if the main wallet is offline. Voting wallet redundancy basically.
Hot wallet will be given voting rights but won't have any coins. The cold wallet will have the coins in it and can be offline. Hot wallet need to be connected to the net always. U can find more here - along with the commands -- https://wiki.decred.org/Solo_Stake_Mining
There is a difference : (1) hot / cold - to keep your money safe (2) redundant / high availability solution - to ensure at least one wallet votes I'd say - please double check - you can setup (1) and then start many voting wallets - as long as they vote on behalf of the main(offline) wallet.
@Shadowlance, I have this redundant wallet setup using Amazon VPS for a Ubuntu server cli instance. I believe they also offer a Windows server platform too. I use the same wallet seed for the VPS and my main computer, but the VPS' dcrwallet.conf file is set to maintain a balance of 100000000 (maybe one day I will get there!) It stays unlocked in the cloud and responds to vote calls but it doesn't purchase tickets. The website is https://aws.amazon.com/ and I believe it's free for 1 year after signing up if you stay under certain usage limits. The usage limits are VERY generous IMO. If you login and check it out, it's the very first option on the AWS console called "EC2" (Virtual servers in the cloud). I'd suggest to check it out for yourself and try to set one up.. it's fairly easy. You can PM me or post up if you get stuck though!
Thanks, @David. I've set up a VPS on AWS before (minecraft server) so I know how to do that. It's the commands to set up the redundant wallet I don't know.
Oh okay sweet! That was a fun game. Here's an example of the config files on my VPS. dcrd.conf: rpcuser=myuser rpcpass=mypass dcrwallet.conf: username=myuser password=mypass enablestakemining=true balancetomaintain=10000000 ticketmaxprice=1 The setup process would be: 1) Start dcrd and let it sync all the way up to the latest block 2) Create your wallet using your seed 3) Start dcrwallet with the settings above and unlock it indefinitely (timeout value of 0) It's essentially the same as anything else, but you are not purchasing tickets. It's a bad idea to purchase tickets or create other transactions from a wallet other than your "main" wallet because the wallets will more than likely get out of sync.
I'll add that, if you aren't doing the hot/cold separation, you can use --reuseaddresses option on dcrwallet, which will make your ticket purchases use only 1 address, so your redundant wallets can see and vote on those tickets fine. If you don't use this, then your redundant wallets won't know about the new addresses of the new tickets you've bought, and you'll need to keep resyncing it.
It means that instead of sending the change and ticket to new addresses, they all get sent to the same address. This means of you have another wallet it'll see all the tickets, as it already knows about the address!
How can I use this command in the dcrctl command to buy tickets. I want ticket address to be a different one( I use stake pool and have to use the wallet address provided by it)
does this mean that :- if I start my dcrwallet with "--reuseaddresses " BEFORE I make an outgoing transaction then any change /returning coins will come back to the same address instead of making a new address ?? cheers
I included this command on the end of .bat file which starts my automatic ticket purchase. Since than I have 840 addresses and this number is not rising anymore.
I tried --enablestakemining --reuseaddresses (just this, not reuseaddresses=XXX) It seemed to work fine, but I checked after a day or so and there were new addresses added ( getaddressesbyaccount default ). I thought no new addresses should appear. I have a version 0.0.9, I did not send out any dcrs, I received some through address got by "getaccountaddress default". Any ideas what could happen ? I can provide 'trace' logs or investigate if you show me the direction.
The simplest explanation might be that --reuseaddresses is only valid for NEW ticket purchases? So your current tickets have been voted you will get new addresses? Just a guess!
i can confirm that as i used my wallet logs & block explorer to verify this. Also if i send a normal tx, i think it creates a new address for change.