🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵

[Ricky Petrovich]

Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant.

Snippet: You can auto-launch with walletpassphrase

BOUNTY TIME !!!

50 bucks to the FIRST correct solution to the linked post in this thread !

https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543

You have to put the RPC config in your conf file:

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=3333

Then you make your call using curl like this:

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["<yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http://<rpcuser>:<rpcpassword>@127.0.0.1:3333



Please send them to this stealth address:
cYBjoey3EfezH2qJDekP4QHiB6zhEykt2BifBVcGgET3GPDbRFsSsxjNg9XXaR2ywzfnnQwvbqkJoRZ pjiHCLYe7UCTot36TMTB1jb

Gracias

Edit: And double Gracias because I learned something new today

Edit2: ["<yourwalletpassword>", 99999, true]
99999 : timeout
true : for staking only

[thc4me]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

[Ricky Petrovich]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

There is no "proper" .conf file. My answer above has nothing to do with the connections issue.

The config file serves the purpose to pass flags to the wallet.

What you include in your config file depends on your needs.

My config:

Code:

maxconnections=999

[iGotSpots]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

maxconnections=999

That's it, or nothing. I have nodes running without a conf file at all. You are only used to using conf files because the coins you use run like shit

[thc4me]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

There is no "proper" .conf file. My answer above has nothing to do with the connections issue.

The config file serves the purpose to pass flags to the wallet.

What you include in your config file depends on your needs.

My config:

Code:

maxconnections=999

I know they can be user need dependant, but some other coins give you an example with proper ports for the coin and a basic starting point.

One taken from the 365coin op page:
Code: (example 365coin.conf)
rpcallowip=*
rpcuser=yourrpcuser
rpcpassword=securerpcpass
rpcport=8869
server=1
daemon=1
listen=1
addnode=50.186.150.238
addnode=69.140.163.94
addnode=80.241.220.178
addnode=37.187.9.53
addnode=50.116.57.160
addnode=80.241.220.178
addnode=164.138.27.175
addnode=212.83.191.214

It gives the proper file name and a starting point config that can be changed/edited later as the user needs change.
It only takes a second or two to do and then at least everyone is using the right info.
It eliminates support issues from users who try to figure it out themselves by trial and error using wrong ports, wrong syntax etc.

[iGotSpots]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

There is no "proper" .conf file. My answer above has nothing to do with the connections issue.

The config file serves the purpose to pass flags to the wallet.

What you include in your config file depends on your needs.

My config:

Code:

maxconnections=999

I know they can be user need dependant, but some other coins give you an example with proper ports for the coin and a basic starting point.

One taken from the 365coin op page:
Code: (example 365coin.conf)
rpcallowip=*
rpcuser=yourrpcuser
rpcpassword=securerpcpass
rpcport=8869
server=1
daemon=1
listen=1
addnode=50.186.150.238
addnode=69.140.163.94
addnode=80.241.220.178
addnode=37.187.9.53
addnode=50.116.57.160
addnode=80.241.220.178
addnode=164.138.27.175
addnode=212.83.191.214

It gives the proper file name and a starting point config that can be changed/edited later as the user needs change.
It only takes a second or two to do and then at least everyone is using the right info.
It eliminates support issues from users who try to figure it out themselves by trial and error using wrong ports, wrong syntax etc.

That's because that coin runs like shit. I included a .bat if you want to edit folders

[thc4me]

I see that lots of people including myself are unclear on what is supposed to be in a proper .conf file.

PLEASE  can someone post a full example of what the contents of the .conf file are that is fully working for this coin.

Nobody has done this and it only causes confusion for all us noobs not totally familiar with what it contains.


Again. Can someone post an actual working .conf file that the noobs can use or modify to their own.

Spots, I don't know why this was not included in the op like most other coins and why nobody has posted one yet after so many have asked for it.

PLEASE PLEASE

There is no "proper" .conf file. My answer above has nothing to do with the connections issue.

The config file serves the purpose to pass flags to the wallet.

What you include in your config file depends on your needs.

My config:

Code:

maxconnections=999

I know they can be user need dependant, but some other coins give you an example with proper ports for the coin and a basic starting point.

One taken from the 365coin op page:
Code: (example 365coin.conf)
rpcallowip=*
rpcuser=yourrpcuser
rpcpassword=securerpcpass
rpcport=8869
server=1
daemon=1
listen=1
addnode=50.186.150.238
addnode=69.140.163.94
addnode=80.241.220.178
addnode=37.187.9.53
addnode=50.116.57.160
addnode=80.241.220.178
addnode=164.138.27.175
addnode=212.83.191.214

It gives the proper file name and a starting point config that can be changed/edited later as the user needs change.
It only takes a second or two to do and then at least everyone is using the right info.
It eliminates support issues from users who try to figure it out themselves by trial and error using wrong ports, wrong syntax etc.

That's because that coin runs like shit. I included a .bat if you want to edit folders

Spots, i only used that as a quick example from a google search.
None of the other coins I have run like shit they are all stable at 8 or more connection all the time without any problems.
I am not at all trying to be a dick here just noticed that alot of people were asking and were not getting any responses.

Why the attitude toward me? I have been nothing but nice to you through this transition.

[iGotSpots]

Why the attitude toward me? I have been nothing but nice to you through this transition.

You act like I've not been helping people. I've written two in-depth guides and been working on connections issues for the past 48 hours straight, which are now resolved

If I don't give a conf example it's because you don't need one unless you want to add maxconnections=999

[thc4me]

Why the attitude toward me? I have been nothing but nice to you through this transition.

You act like I've not been helping people. I've written two in-depth guides and been working on connections issues for the past 48 hours straight, which are now resolved

If I don't give a conf example it's because you don't need one unless you want to add maxconnections=999

Fair enough.
I don't see anything i have written that implies that, but OK I will ask no more questions.

By the way the latest fixes have worked great, I now have 10 connections. Thanks for your hard work.

[iGotSpots]

Why the attitude toward me? I have been nothing but nice to you through this transition.

You act like I've not been helping people. I've written two in-depth guides and been working on connections issues for the past 48 hours straight, which are now resolved

If I don't give a conf example it's because you don't need one unless you want to add maxconnections=999

Fair enough.
I don't see anything i have written that implies that, but OK I will ask no more questions.

By the way the latest fixes have worked great, I now have 10 connections. Thanks for your hard work.

Sorry, I'm stressed. Glad it's working. There really is no need for a conf file, though, other than that one line if you want it

[iGotSpots]

Most of those commands you posted are for mining or servers, which are not needed here, either, so it would just be forcing your client to run less lightweight and be more of a resource hog than it needs to be

Remember, some people are running a bunch of masternodes on one machine, so usage is important to keep low

[nembot]

10 connections now, more than I ever had for MMXIV.  Thanks - something obviously worked.

If anyone still struggling you can try this, most people know all these basics but not so long ago I didn't. So if you know how do do this just ignore & sorry to be basic...

I'm on Windows - actually on a Windows virtual machine on a mac (downloaded VMware fusion and a 64-bit Windows 8 image from a famous file-hosting site)

First make sure you can see hidden folders - go to control panel, type "folders" in the search box and select "show hidden files and folders".

Close down GorillaBucks client.

Then go to C:/Users/your name/AppData/Roaming/GorillaBucks (you won't see the AppData folder unless you have shown hidden folders)

Be very careful here, don't delete anything permanently until you are sure you have done this right - but basically delete or move out of the folder, everything apart from the wallet.dat

Now make a new Text Document in there and rename it:
 GorillaBucks.conf
(to open it again you may need to say "open as text document")

That's a conf file.  As iGotSpots says many people are running fine without one, or with the only contents being:

maxconnections=999

My conf file is as follows, using the addnodes iGS gave us earlier:

maxconnections=999
addnode=195.23.251.183
addnode=171.96.245.177
addnode=68.224.26.233
addnode=83.131.214.162
addnode=99.7.21.54
addnode=98.193.42.19
addnode=173.81.239.170
addnode=137.224.252.10
addnode=86.121.63.75
addnode=80.136.69.94
addnode=39.55.166.152
addnode=70.92.184.203
addnode=217.217.234.127
addnode=192.99.184.36
addnode=197.2.161.89
addnode=131.188.203.228
addnode=75.130.163.51
addnode=82.13.20.194
addnode=192.226.139.105
addnode=98.144.3.64
addnode=220.244.154.64
addnode=192.99.184.36
addnode=79.37.237.149
addnode=93.86.200.129
addnode=32.214.108.194
addnode=75.130.163.51
addnode=101.51.49.130
addnode=75.130.163.51
addnode=49.228.141.168
addnode=73.12.7.191
addnode=71.228.74.170
addnode=1.20.244.211
addnode=60.240.164.100
addnode=69.196.133.53
addnode=100.3.192.41
addnode=94.52.19.22
addnode=60.240.164.100
addnode=5.157.107.66
addnode=24.35.140.35
addnode=60.240.164.100
addnode=174.17.128.72
addnode=68.224.6.180
addnode=31.217.43.152
addnode=78.214.244.90
addnode=76.90.105.71
addnode=23.127.64.254
addnode=83.145.242.175
addnode=178.33.64.235
addnode=104.236.183.29
addnode=69.165.47.72
addnode=84.91.18.158
addnode=23.115.188.142
addnode=83.157.62.179
addnode=39.55.166.152

Hope that helps someone, good luck to all

[MoreBloodWine]

Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant.

Snippet: You can auto-launch with walletpassphrase

BOUNTY TIME !!!

50 bucks to the FIRST correct solution to the linked post in this thread !

https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543

You have to put the RPC config in your conf file:

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=3333

Then you make your call using curl like this:

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["<yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http://<rpcuser>:<rpcpassword>@127.0.0.1:3333



Please send them to this stealth address:
cYBjoey3EfezH2qJDekP4QHiB6zhEykt2BifBVcGgET3GPDbRFsSsxjNg9XXaR2ywzfnnQwvbqkJoRZ pjiHCLYe7UCTot36TMTB1jb

Gracias

Edit: And double Gracias because I learned something new today

Edit2: ["<yourwalletpassword>", 99999, true]
99999 : timeout
true : for staking only

I'll give this a shot and get back to you by tomorrow at the latest.

Also, does anyone else find they need to "unlock for staking only to keep the bands running ?

Had one band unlocked the other locked and the locked one strangely enough seemed to be the bread winner. So not sure what all still does or doesn't need to be done to get the most out of my bands. IGS said he doesnt use confs but I don't believe has started his type of setup like r his wallet excrypted, has he tried a system reboot or two with wallet launch on startup etc.

Ty.

[elgimpo]

Also, does anyone else find they need to "unlock for staking only to keep the bands running ?

Had one band unlocked the other locked and the locked one strangely enough seemed to be the bread winner. So not sure what all still does or doesn't need to be done to get the most out of my bands. IGS said he doesnt use confs but I don't believe has started his type of setup like r his wallet excrypted, has he tried a system reboot or two with wallet launch on startup etc.

Ty.

The debug.log suggests the masternode needs to be unlocked (for staking) to register as a masternode, but I am unsure about the need to keep it unlocked thereafter.
Ive kept mine in an unlocked for staking state just to be sure.

One thing I am trying to figure out is the queue order of masternode payments, they dont seem sequential to me.

[iGotSpots]

All caught up on swaps again. Everyone should have all their coins now

[notabeliever]

Most of those commands you posted are for mining or servers, which are not needed here, either, so it would just be forcing your client to run less lightweight and be more of a resource hog than it needs to be

Remember, some people are running a bunch of masternodes on one machine, so usage is important to keep low

Yes no config works better.  Any time to see why I loose my stakinging credits? If Gorrillabands get 50% of them I see  full debits of credits.

[iGotSpots]

Most of those commands you posted are for mining or servers, which are not needed here, either, so it would just be forcing your client to run less lightweight and be more of a resource hog than it needs to be

Remember, some people are running a bunch of masternodes on one machine, so usage is important to keep low

Yes no config works better.  Any time to see why I loose my stakinging credits? If Gorrillabands get 50% of them I see  full debits of credits.

I have some time now for issues like this, please copy paste an example and I'll take a look

[iGotSpots]

The bottom one is not a valid transaction

[iGotSpots]

Just orphans. The network is super packed right now, they are bound to happen for a little while until it smooths out

[notabeliever]

Just orphans. The network is super packed right now, they are bound to happen for a little while until it smooths out

Okay then all set thanks