MoreBloodWine
New member
Ok, so here's my issue which is taken from the DASH bitcointalk thread: topic=421615.msg11913461#msg11913461
GorillaBucks.conf
masternode.conf
I dable in dash trying to learn as much as I can about it before gets getting to serious with it but I am curious if someone can maybe help me with something relating to the "new" Gorilla Bucks (BUCKS) which has masternodes based of off bananabits which I assume is based on DASH.
If anyone can or is willing to help great and if not, Thx ne way.
The below is a copy of a PM I sent to someone else that doesn't seem able to help with possibly resolving the "issue".
Cool.
This is the original guide I followed to set up two remote nodes / bands with two cold / locked local wallets which is currently working pretty flawlessly using the start n stop commands etc.
https://dashtalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/
This is the guide I'm trying to use to control both remote nodes / bands with one local cold / locked wallet using option B (Consolidation - transfer several "old" wallets into one new wallet.).
https://dashtalk.org/threads/reuben...rnodes-from-one-wallet-guide-start-many.4034/
I've followed both guides to a T with the first one succeeding and just failing on the latest one where I am trying to use the the one local to control multiple remotes. At one point someone suggested IGotSpots mighta done something to fault masternode.conf but he said it "should" be able to work even though it's not needed hinting the way he has the easy band setup is the way to go but not quite ideal for some people such as myself.
But ya, if you check out the linked post you'll see where I mention I get expected outputs with "masternode outputs" but when running "masternode list-conf" I get nothing where I should be seeing the info from masternode.conf parsed in the console and not just seeing {} or w/e it is.
Even when I use start or start-many nothing "starts" since the systems for all intensive purposes sees the masternode.conf file as empty.
Ty BTW.
So now that that's out of the way, here's what my masternode.conf file looks like. Only guide not linked is the last one I found where it was said that a donation address can be used to have the MN payments sent.
GorillaBand1 <IP:11839> <MN PRIV KEY> <TX HASH> 1 <donation address>
GorillaBand2 <IP:11840> <MN PRIV KEY> <TX HASH> 1 <donation address>
Ps; While I cannot offer a bounty in DASH, I can offer one in BUCKS if it helps entice someones assistance, Ty.
Edit: I suspect just getting / figuring out why "masternode list-conf" doesn't output the stuff in my masternode.conf file is the only thing we'll need to figure out since when using something like start many should start the nodes otherwise found in the masternode.conf file even though that's only 2 for me right now.
GorillaBucks.conf
rpcuser=<user>
rpcpassword=<pass>
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
port=11839
staking=0
maxconnections=9999
masternode.conf
GorillaBand1 45.63.18.81:11839 <MN KEY> 4c3db17952e0cd742b5e297b906309ce1f6bb252e3104223b1789c24cabffa75 1 BBFNytsouQsskUzmspDWs2k3KPEqxQPbi5
GorillaBand2 45.63.19.64:11839 <MN KEY> cb2caffd895f5cb37d940bbd5c1b9b552c3cb01fa8ab232eb1fc2ef0080dc1eb 1 BBFNytsouQsskUzmspDWs2k3KPEqxQPbi5