Topic: 🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵 - page 28. (Read 133306 times)
July 03, 2015, 08:42:44 PM
It's a known, but sporadic, issue that I'm working on nailing down
July 03, 2015, 07:46:18 PM
@IGS: But why all of a sudden would I be getting this "error" now when everything's ran fine up to three clients since launch ?
July 03, 2015, 07:04:58 PM
July 03, 2015, 07:02:42 PM
In ohio right now with family so I'm monitoring remotely as the image shows but I'm curious if you, IGS, might have an idea on why all of a sudden I'm seeing / getting this on one of my two clients.
The machine is win 7 64 bit, the one crashing is the main client run from the exe where as the second which seems to be holding fine is run from a shortcut with the target trick.
The machine is win 7 64 bit, the one crashing is the main client run from the exe where as the second which seems to be holding fine is run from a shortcut with the target trick.
Paul came up with a bandaid fix for this for now
Run with XP-Compatibility and it shouldn't crash again. It's a known, but sporadic, issue that I'm working on nailing down
July 03, 2015, 07:01:43 PM
In ohio right now with family so I'm monitoring remotely as the image shows but I'm curious if you, IGS, might have an idea on why all of a sudden I'm seeing / getting this on one of my two clients.
The machine is win 7 64 bit, the one crashing is the main client run from the exe where as the second which seems to be holding fine is run from a shortcut with the target trick.
The machine is win 7 64 bit, the one crashing is the main client run from the exe where as the second which seems to be holding fine is run from a shortcut with the target trick.
July 03, 2015, 06:24:04 PM
All I've done is open up the proper ports in the virtual server on my router. The router is like 5 or 6 years old...I have allowed private connections in my firewall but not public connections for my wallets with my OS firewall. Am I supposed to allow public connections?
You should open port on router AND firewall from os.Right now only outgoing connections are possible, getpeerinfo in debug should confirm this.
I'm not even sure what I am looking at. I don't think it would be advisable for me to open all the ports.
addr" : "23.92.61.98:65391",
"addrlocal" : "71.237.125.226:36480",
"services" : "00000001",
"lastsend" : 1435942579,
"lastrecv" : 1435942579,
"bytessent" : 5923256,
"bytesrecv" : 5071591,
"conntime" : 1435904087,
"pingtime" : 0.15900900,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : true,
"startingheight" : 5017,
"banscore" : 0,
"syncnode" : false
"inbound" : true
inbound = incoming if true you are indeed getting incoming connections.
Of course you should never open all ports, just the one that your app needs.
But you just had the connection limit problem.
Should have thought about that one, but I always use my own default conf file for any QT wallet and my default setting is maxconnections=100.
Anyway just a short while ago I had the same problem only 2 connection outgoing only.
This happened after I made some changes in my port settings from my router.
So easy to relate and a restart solved it.
Also a standard thing to try when you have strange things happening after installing software/hardware or playing with a router.
Reboot or restart !
July 03, 2015, 06:11:01 PM
waw , bucks appeared dittrex
July 03, 2015, 05:13:03 PM
put more buy support on bittrex. 2.4 is too low
July 03, 2015, 04:01:49 PM
Thanks Richie!
July 03, 2015, 03:24:28 PM
Ok great thanks. Sounds like a bit more than with staking so I'll probably come over to the dark side
But if more GBs are active you make less I suppose
But if more GBs are active you make less I suppose
July 03, 2015, 03:16:44 PM
Between 80-140 a day per GBand right now, depending on how many are active. We're up over 80 now and it keeps increasing. That's over 40% of the total supply, plus there is still like 10% not swapped over yet
July 03, 2015, 03:13:46 PM
Thanks for the technicals. Any answer as to whether MNs or staking 5000 is the best at the moment?
Anyone got any figures for how much the Gorillabands are making? baldpope?
Anyone got any figures for how much the Gorillabands are making? baldpope?
July 03, 2015, 03:11:13 PM
don't sell your coins cheep . why some people sell there coin very cheep.
now on bittrex we can make the price
now on bittrex we can make the price
July 03, 2015, 02:59:08 PM
Variance Staking Explained
Now that we've all had a few days to get used to the new blockchain and wallet, there have been a few questions to how much people will stake on their deposits. While the changes are not over-the-top complicated, they do change the basic fundamentals of how rewards are calculated. I wanted to take a few minutes to explain exactly what Variance Staking means
First, I'll just copy the code from Github, which makes it pretty self explanatory when you see it singled out. Please note there are a few extra spaces that are not on Github, only because it was making emoticons with them on the forums. With that being said, let's get into it
nMultiplier is simply used as a tweaking dial that can be turned up or down as needed to control inflation. Using 100 * CENT just gives us full coins, rather than decimals. The main reason is just so this is here later to change if needed, it really serves no purpose other than to do calculations in full coins
The line we are going to look at and break down is this:
int64_t nSubsidy = (((nHeight % 9) + ((nCoinAge % 100000) * 33 / (365 * 33 + 8 ))) + 1) * nMultiplier;
nSubsidy is the final reward that will be passed later on. nHeight is block number and nCoinAge is obvious
nHeight % 9 will take the block number, divide it by 9 and return the remainder as the value
This number will always be between 0 and 9 (the base rewards we have been seeing so far)
nCoinage % 100000 will allow a maximum coinage of 100,000 to be used, which is then multiplied by '(33 / (365 * 33 + 8 )' or 0.00273790757, to scale it down further and prevent compounding inflation
This will return a value somewhere between 0 and 273.790757488
The final +1 is there for one simple reason.. while doing test runs this problem never came up, but I noticed that it could potentially in the future.. If that last +1 was not there, as unlikely as it is, we could have run into a 'divide by zero' issue while calculating or splitting rewards, so that is just a failsafe to ensure we never return 0 as the value (this was originaly was nHeight calculation is in, but was later replaced. nHeight is only used now to fluctuate rewards for deposits that are not large enough to be scaled by coinage)
Last, as explained above, nMultiplier is only used to turn the final result into a full number, rather than a long reward amount with a staggering amount of decimal places
Hopefully this will clear up a bit on what you can expect both now and for the future as far as staking and GorillaBand rewards. The later in the life of the coin we get, with higher coinage, the faster GorillaBands will pay themselves off. At current rates for now, you are doubling your coins in less than a month
TL;DR: Rewards will be between 1.0 and about 284 for the life of the coin if no updates are required
Now that we've all had a few days to get used to the new blockchain and wallet, there have been a few questions to how much people will stake on their deposits. While the changes are not over-the-top complicated, they do change the basic fundamentals of how rewards are calculated. I wanted to take a few minutes to explain exactly what Variance Staking means
First, I'll just copy the code from Github, which makes it pretty self explanatory when you see it singled out. Please note there are a few extra spaces that are not on Github, only because it was making emoticons with them on the forums. With that being said, let's get into it
Code:
int64_t GetProofOfStakeReward(int nHeight, int64_t nCoinAge, int64_t nFees)
{
int64_t nMultiplier = 100 * CENT;
int64_t nSubsidy = (((nHeight % 9) + ((nCoinAge % 100000) * 33 / (365 * 33 + 8 ))) + 1) * nMultiplier;
a + b
return nSubsidy;
}
nMultiplier is simply used as a tweaking dial that can be turned up or down as needed to control inflation. Using 100 * CENT just gives us full coins, rather than decimals. The main reason is just so this is here later to change if needed, it really serves no purpose other than to do calculations in full coins
The line we are going to look at and break down is this:
int64_t nSubsidy = (((nHeight % 9) + ((nCoinAge % 100000) * 33 / (365 * 33 + 8 ))) + 1) * nMultiplier;
nSubsidy is the final reward that will be passed later on. nHeight is block number and nCoinAge is obvious
nHeight % 9 will take the block number, divide it by 9 and return the remainder as the value
This number will always be between 0 and 9 (the base rewards we have been seeing so far)
nCoinage % 100000 will allow a maximum coinage of 100,000 to be used, which is then multiplied by '(33 / (365 * 33 + 8 )' or 0.00273790757, to scale it down further and prevent compounding inflation
This will return a value somewhere between 0 and 273.790757488
The final +1 is there for one simple reason.. while doing test runs this problem never came up, but I noticed that it could potentially in the future.. If that last +1 was not there, as unlikely as it is, we could have run into a 'divide by zero' issue while calculating or splitting rewards, so that is just a failsafe to ensure we never return 0 as the value (this was originaly was nHeight calculation is in, but was later replaced. nHeight is only used now to fluctuate rewards for deposits that are not large enough to be scaled by coinage)
Last, as explained above, nMultiplier is only used to turn the final result into a full number, rather than a long reward amount with a staggering amount of decimal places
Hopefully this will clear up a bit on what you can expect both now and for the future as far as staking and GorillaBand rewards. The later in the life of the coin we get, with higher coinage, the faster GorillaBands will pay themselves off. At current rates for now, you are doubling your coins in less than a month
TL;DR: Rewards will be between 1.0 and about 284 for the life of the coin if no updates are required
July 03, 2015, 01:48:00 PM
Is BUCKS broken on c-cex? my coins have been stuck at 2 confirms for over a day.
Confirms come about 1 per min
July 03, 2015, 01:26:45 PM
Is BUCKS broken on c-cex? my coins have been stuck at 2 confirms for over a day.
July 03, 2015, 12:43:54 PM
36480 is probably the port you want to open, although your info makes me think ports are fine
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
I should have just did that in the first place. But I'm so used to only having 8 connections or less with my other wallets, I was convinced it was my old router. Now I have 58 and climbing. Thanks.
Np, this is not your usual wallet. Expect more!
July 03, 2015, 12:40:35 PM
36480 is probably the port you want to open, although your info makes me think ports are fine
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
I should have just did that in the first place. But I'm so used to only having 8 connections or less with my other wallets, I was convinced it was my old router. Now I have 58 and climbing. Thanks.
July 03, 2015, 12:29:22 PM
36480 is probably the port you want to open, although your info makes me think ports are fine
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
Make sure GorillaBucks.conf has
maxconnections=999
That's a ghetto way, for now, to make sure you catch all possible peers, regardless of IPv
July 03, 2015, 12:20:47 PM
All I've done is open up the proper ports in the virtual server on my router. The router is like 5 or 6 years old...I have allowed private connections in my firewall but not public connections for my wallets with my OS firewall. Am I supposed to allow public connections?
You should open port on router AND firewall from os.Right now only outgoing connections are possible, getpeerinfo in debug should confirm this.
I'm not even sure what I am looking at. I don't think it would be advisable for me to open all the ports.
addr" : "23.92.61.98:65391",
"addrlocal" : "71.237.125.226:36480",
"services" : "00000001",
"lastsend" : 1435942579,
"lastrecv" : 1435942579,
"bytessent" : 5923256,
"bytesrecv" : 5071591,
"conntime" : 1435904087,
"pingtime" : 0.15900900,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : true,
"startingheight" : 5017,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "151.229.219.75:36480",
"addrlocal" : "71.237.125.226:58814",
"services" : "00000001",
"lastsend" : 1435942578,
"lastrecv" : 1435942571,
"bytessent" : 5157906,
"bytesrecv" : 5115162,
"conntime" : 1435908187,
"pingtime" : 0.25301400,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 5071,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "68.224.6.180:36480",
"addrlocal" : "71.237.125.226:49416",
"services" : "00000001",
"lastsend" : 1435942578,
"lastrecv" : 1435942572,
"bytessent" : 4148591,
"bytesrecv" : 4095923,
"conntime" : 1435916672,
"pingtime" : 0.16401000,
"version" : 61400,
"subver" : "/GorillaBucks:6.4.8/",
"inbound" : false,
"startingheight" : 5180,
"banscore" : 0,
"syncnode" : false
Jump to: