Topic: 🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵 - page 56. (Read 133306 times)
June 28, 2015, 09:44:51 PM
Connections good here too, seednode restart seems to have done the trick.
June 28, 2015, 09:44:18 PM
2 active connections now Spots. Thank you.
now 24 active connectionsty spot
June 28, 2015, 09:40:46 PM
2 active connections now Spots. Thank you.
June 28, 2015, 09:39:02 PM
I've restarted a few seednodes. Let me know if connections get better
If you're still having issues, just restart wallet and REMOVE ALL ADDNODES - You don't need them
June 28, 2015, 09:36:48 PM
I've restarted a few seednodes. Let me know if connections get better
June 28, 2015, 09:35:00 PM
My wallet has been opened for 2 hours now, still no connections.
Added GorillaBucks.conf in data roaming. It added a peer.dat file, but no connections as of yet.
Peace, Dennis
P.S. have not sent any privkeys as if it is not connecting, will not get any confirms acknowledging coins.
Added GorillaBucks.conf in data roaming. It added a peer.dat file, but no connections as of yet.
Peace, Dennis
P.S. have not sent any privkeys as if it is not connecting, will not get any confirms acknowledging coins.
I add to .conf
port=36482
and my wallet find 1 node immediately
46.255.168.83:36480
June 28, 2015, 09:31:29 PM
Ok, I've made it through most of MMXIV now, and all the Variance wallet.dat's that were sent. PRIVATE KEYS ARE NOT SUFFICIENT FOR VARIANCE
All caught up on all the BUCKS and TEETH keys sent in so far
Please send your VARIANCE wallet.dat to
[email protected]
Include password if it is locked. Having issues with keys not rescanning the snapshot
Other 3 coins are fine, this is JUST FOR VARIANCE
All caught up on all the BUCKS and TEETH keys sent in so far
Please send your VARIANCE wallet.dat to
[email protected]
Include password if it is locked. Having issues with keys not rescanning the snapshot
Other 3 coins are fine, this is JUST FOR VARIANCE
Oh shit. I stuck my VARY into a paper wallet. Does that mean I get screwed?
June 28, 2015, 09:28:09 PM
My wallet has been opened for 2 hours now, still no connections.
Added GorillaBucks.conf in data roaming. It added a peer.dat file, but no connections as of yet.
Peace, Dennis
P.S. have not sent any privkeys as if it is not connecting, will not get any confirms acknowledging coins.
Added GorillaBucks.conf in data roaming. It added a peer.dat file, but no connections as of yet.
Peace, Dennis
P.S. have not sent any privkeys as if it is not connecting, will not get any confirms acknowledging coins.
June 28, 2015, 09:20:18 PM
Thx, seems to work. I didn't specify port as I'll just add a conf file to the secondary roaming folder.
I got creative and created a video - http://youtu.be/Mi45mtv5vaY
June 28, 2015, 09:19:56 PM
stil 0 connection and having this in .conf :
addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"
Same trouble addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"

getpeerinfo
04:19:15

[
{
"addr" : "179.25.221.22:54906",
"services" : "00000001",
"lastsend" : 1435544320,
"lastrecv" : 1435544347,
"bytessent" : 3029,
"bytesrecv" : 10577,
"conntime" : 1435544078,
"pingtime" : 0.48002700,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : true,
"startingheight" : 221,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "75.130.163.51:65454",
"services" : "00000001",
"lastsend" : 1435544347,
"lastrecv" : 1435544347,
"bytessent" : 959,
"bytesrecv" : 1526,
"conntime" : 1435544128,
"pingtime" : 0.33801900,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : true,
"startingheight" : 222,
"banscore" : 0,
"syncnode" : false
}
]
June 28, 2015, 09:15:39 PM
stil 0 connection and having this in .conf :
addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"
Same trouble addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"
June 28, 2015, 09:14:58 PM
stil 0 connection and having this in .conf :
addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"
addnode=23.92.61.98
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
addnode=82.44.30.10
addnode=108.91.73.3
addnode=84.104.68.59
addnode=71.237.125.226
addnode=178.33.64.235
addnode=71.228.74.170
addnode=81.227.243.16
addnode=82.47.20.169
addnode=192.226.139.105
addnode=99.137.226.94
addnode=75.130.163.51
debug.log gives lots of "socket recv error 10054"
June 28, 2015, 09:11:58 PM
If The cmd window that opens when running the second node, can it be closed after the client launches or does it have to remain open ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
review the command line options and instead of running it from the bat file, place a shortcut on your desktop pointing to the binary and modify it. under the 'target' include the same command line options from the bat file. each short-cut would have it's own set of options (specific to each MN directory).
hope that helps.
baldpope
open the .bat file in notepad - you'll see the following:
GorillaBucks-Qt.exe -datadir=masternodedirectory -port=36482 -rpcport=36482
Instead of running those from the bat file (which is OK I suppose) you can create a shortcut to the QT executable on your desktop (right-click on qt and drag to desktop -> release -> create shortcut).
then right click on shortcut, select properties, and on the Target line, add in -datadir -port -rpcport and any other qt options. apply/save the settings. then when you double-click on the shortcut it'll execute with those options.
in this way, you can create multiple short cuts each with their own -datadir and port directives.
hth
June 28, 2015, 09:07:57 PM
Ok, update time
BUCKS ✔
MMXIV ✔
TEETH ✔
VARY ✔
BUCKS ✔
MMXIV ✔
TEETH ✔
VARY ✔
June 28, 2015, 09:04:00 PM
If The cmd window that opens when running the second node, can it be closed after the client launches or does it have to remain open ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
review the command line options and instead of running it from the bat file, place a shortcut on your desktop pointing to the binary and modify it. under the 'target' include the same command line options from the bat file. each short-cut would have it's own set of options (specific to each MN directory).
hope that helps.
baldpope
open the .bat file in notepad - you'll see the following:
GorillaBucks-Qt.exe -datadir=masternodedirectory -port=36482 -rpcport=36482
Instead of running those from the bat file (which is OK I suppose) you can create a shortcut to the QT executable on your desktop (right-click on qt and drag to desktop -> release -> create shortcut).
then right click on shortcut, select properties, and on the Target line, add in -datadir -port -rpcport and any other qt options. apply/save the settings. then when you double-click on the shortcut it'll execute with those options.
in this way, you can create multiple short cuts each with their own -datadir and port directives.
hth
June 28, 2015, 08:49:39 PM
I have 8 addresses inside MMXIV wallet which privkey I need dump? Or i need send all coins to one address?
Thank You
Thank You
Since it is too late to move any coins you will need to get the private key for each of your addresses.
June 28, 2015, 08:44:51 PM
I have 8 addresses inside MMXIV wallet which privkey I need dump? Or i need send all coins to one address?
Thank You
Thank You
June 28, 2015, 08:37:13 PM
If The cmd window that opens when running the second node, can it be closed after the client launches or does it have to remain open ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
review the command line options and instead of running it from the bat file, place a shortcut on your desktop pointing to the binary and modify it. under the 'target' include the same command line options from the bat file. each short-cut would have it's own set of options (specific to each MN directory).
hope that helps.
baldpope
June 28, 2015, 08:36:12 PM
Ok, I've made it through most of MMXIV now, and all the Variance wallet.dat's that were sent. PRIVATE KEYS ARE NOT SUFFICIENT FOR VARIANCE
All caught up on all the BUCKS and TEETH keys sent in so far
Please send your VARIANCE wallet.dat to
[email protected]
Include password if it is locked. Having issues with keys not rescanning the snapshot
Other 3 coins are fine, this is JUST FOR VARIANCE
All caught up on all the BUCKS and TEETH keys sent in so far
Please send your VARIANCE wallet.dat to
[email protected]
Include password if it is locked. Having issues with keys not rescanning the snapshot
Other 3 coins are fine, this is JUST FOR VARIANCE
June 28, 2015, 08:32:55 PM
If The cmd window that opens when running the second node, can it be closed after the client launches or does it have to remain open ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
If it can be closed, how / what might one add to the batch file so it closes after the clients launched and connected to the "secondary" roaming folder ?
review the command line options and instead of running it from the bat file, place a shortcut on your desktop pointing to the binary and modify it. under the 'target' include the same command line options from the bat file. each short-cut would have it's own set of options (specific to each MN directory).
hope that helps.
baldpope
Jump to: