There's a guide on
GorillaStake.com/gorillabands.htmlSetting up multiple GorillaBands on one machine is easy and takes only a few extra minutes. Please follow the guide below to complete setup in moments
First, navigate to Roaming and find the GorillaBucks folder. This is the folder and path you will want to remember for the second step. Copy this entire folder (except wallet.dat) and rename to Roaming/GorillaBucksMasternode1
Next, edit the batch file that was included in your wallet download and replace 'masternodedirectory' with the file location copied from above, (example: ../Roaming/GorillaBucksMasternode1). If this is the only additional GorillaBand you plan on setting up, then you can close the .bat edit window now and launch the client using this file. If you plan on setting up a third, fourth.. GorillaBand on the same machine, continue on with the simple step by step instructions below
By now you have your first GorillaBand set up, so this will be easy! Simply copy the batch file (GorillaBand.bat) and change the datadir and ports to unique and unused folders and ports. Each instance of the wallet will need a new folder and port assigned to it. Simply copy the batch file and change a few flags to set up multiple GorillaBands on one machine, saving on rentals and maintenance
I brain farted and figured it out. But if you could PLEASE answer one final thing for me I've sorta been harping on, I can promise you wont hear another peep from me in the support area. Seeing as how the only thing after this question is the connection thing your actively working on. But ya, if you could please do me this one SOLID I would reallllllllly appreciate it m8.
Ok, thanks
You can auto-launch with walletpassphrase if your end-game is trying to automate it, which is what it seems like to me
Ya because I have the local machine on a weekly reboot.
But it makes sense it would need to be that way since earned BUCKS are staked until some confs come in.
But can you assist me with a demo of what you mean please ?
Ty.
Edit: I don't want to auto launch with the pasphrase if it wont be a "unlock for staking only" situation and not a auto launch which results in a fully unlocked unsecure band.
I figured out that walletpassphrase <secret> 99999 true is what needs to be used but not sure where it goes how it needs to be set up to be passed on wallet load.
Still running in to issue with bands and did some reading on the vin message me n others have gotten and want to try a few tricks but this "the above" plays heavily in to my testing.
