This is why I didn't want to try and compile it myself lol...

iGotSpots you can write off on my pm? And reasonably conclude this, I'll be happy with anything;]

@spots I have btc withdrawal waiting for admin approval in gorilla exchange, how long it gonna take? Its already 6 hours? 

Not what I asked but thats cool lol

So if you don't mind me beating the proverbial dead horse lol, is there a linux install planned ?

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

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.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.

Is BUCKS broken on c-cex? my coins have been stuck at 2 confirms for over a day.

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.

http://www2.zippyshare.com/v/d3m1DAGk/file.html

Here is my picture, and what to do with it next? is this okay or not? and why I don't gain any coin since the 30th? what can I do..