Sorry, I thought I posted this on the forums as well but apparently I only talked about it on IRC [it occurred while I was at work]:

There was a small problem due to closing I0 Guild.  The code is literally a copy of BTC Guild, with an added flag at run time which tells it not to sync round data with the master server.  When I shut down I0 Guild, I realized that the payouts would likely not make it to the exchange in time for what looks like a bug that will completely destroy the I0 Coin fork until its patched and everybody updates.  So I turned the pool server back on, to help push the coins to the exchange for the last payouts.

The no-sync flag was not included, so when I0Guild found an i0 block, it pushed a new round to the master server which caused some 2547 shares to be logged as 2548.  I caught it at 2549.  The total time-shifting was about 1h 30 minutes, thus the time differences on 2547/2548 vs BlockExplorer.  At that point 2547 had already been calculated.  I made the decision to leave the shares alone, rather than risk duplicating or not counting some shares.  The effect on payouts would have been negligible, and altering rewards which already showed up as confirmed is something I would only do if there was a major problem.


I've gone in and corrected the end/start times of those rounds to keep them in line with the actual times per Block Explorer.  It makes the estimated hash rates for those blocks a bit off, but it keeps our database in line with actual block data, which is more important than things like estimated hash rates.  The problem that happened at I0 Guild is one that can't be repeated on SC Guild since it is on a different physical server that cannot access the MySQL servers on BTC Guild.  Future forks if they arise will also be launched on non-BTC Guild servers both as a precaution, and to avoid putting unrelated load on the BTC Guild servers.

This is something I will be fixing soon.  The way block finders are recorded was drastically changed from the original code back when we were in our first 200 rounds, due to splitting up the servers.  The API still tries to pull that information from old data.

Really nothing I can do at this point.  You can't disprove a negative.  You can prove someone stole, you can't prove someone didn't steal.  At this point I can just sit here arguing or ignore it, and I'm choosing the latter.  The last time I responded I gave our stats over the last few difficulties that I had recorded and display. It showed about a 20% chance of our luck over the recorded difficulties using Vladmir's method to calculate the probability with a Poisson distribution calculator.  I didn't bother going back into the past because I did not track difficulties/luck at previous levels, so I would've had to hunt down the proper block #s and calculate our luck for each one at a time where I was trying to respond to the witch hunt as quickly as possible.

All I know is there were a LOT of software problems between June and July, which was when we were massively expanding (peaking at 8 servers).  There were times where servers ran with duplicate wallet files (meaning they were [possibly] hashing the same headers/duplicating work).  There were times where the pools were going up/down regularly, which I believe caused them to resend the same getwork space a few times thus awarding shares to duplicate work due to the crashes.  And there were the JoelKatz patches trying to keep up with scaling the servers which had a number of issues before becoming stable.

At this point I'll just let http://l0ss.net do the talking, which is monitoring the luck for 6 of the largest pools, now with nearly 1 month of time included.  We swing up, we swing down, and I have no desire to make my life a living hell by refreshing our block page every 15 minutes to see which way we're swinging.

EDIT:  I can definitely say his method of adding shares from invalids to other blocks skews results further in his favor, since our invalid rate in that time was much higher due to server attacks, botnets making our connections unreliable, and the problems implementing JoelKatz' patches.  Still looks bad, but as I said at the start:  It's not possible to disprove the assertion.

No, but you can see the list of blocks getting the bonus on the front page.  The bonuses appear once the randomly selected round has been completed.  If it later becomes orphaned I'll add a new round into the list to award the bonus.

We already have the largest pool, though we're under 50% unlike i0c where we definitely passed 50% right out of the gate.  If we start solving 60 out of the previous 120 blocks I'll probably close registrations.  I like the idea of a currency which can maintain a steady trade rate with BTC outside of physical "real currency".

Nice to see the steady difficulty rise, so much better than the abrupt cliffs of i0coin/ixcoin/namecoin.

I think Solidcoin made one great change that makes it viable for a secondary market for BTC.  While I don't currently anticipate a new coin coming out that becomes a viable currency for online stores, I do think SolidCoin's difficulty retarget method makes it a tool for non-USD BTC exchange.

The 10% limit on growth while maintaining the 75% fall in difficulty on a 240 block/12 hour window means it is immune to what happened to I0C/IXC, where the flood of miners hit the currency and vanished when BTC became higher valued.

Whether or not the speculation secondary market can survive can't be predicted, but at least SC had the right idea when it came to difficulty readjustment period for a competing/alternate cryptocurrency.

SC Guild has become the first pool to pass 100 GH/s (and still rising).  We'll be splitting 1,000 SC of the 2,500 bounty with miners on random rounds after it has been received.  Address for bounty: sQS2JPDdtzpXmoTKAJgvZgK94BYNuouHUv


https://i.imgur.com/1z6Ow.jpg - Link of proof (or just go to http://sc.btcguild.com to see it live).

FYI:  I strongly recommend CG Miner for mining in general, but even moreso for BTC forks at low difficulties.  CGMiner is the king of fast long poll handling, with the lowest reject rates BY FAR.

Pool is now obviously Solidcoin (all i0c references removed).

If we reach the 100 GH/s required for the bounty, I'll be taking 1000 coins out of the 2500 bounty and selecting 10 round IDs at random (future rounds) to allocate a bonus 100 SC block reward among the miners.

SolidCoin pooling is up from BTC Guild:  http://sc.btcguild.com

Currently still has the I0C branding, being removed over the next few minutes.

Its already back up, total downtime was about an hour.

A few people probably saw funny looking stats in the last 6 hours.  Yesterday I put up a 4th pool instance on US West since it has been getting a bit more load than Central.  4th pool worked fine, except I missed the rpcallowip in bitcoin.conf.  The pool found a few blocks, but the master server couldn't poll bitcoind them to get the txid/fees included in the block.

This has been resolved.  Due to the way the servers handle rounds, no round share data was lost, simply the rounds for found blocks are slightly jumbled in their confirmation counts.

Yeah, made a bit more than expected.  I thought i0guild would peak at just over 100 GH/s, thus the performance problems from having 400+ GH/s pointed at it.  I mostly just wanted to fork BTC Guild to a standalone package anyways, and I was pretty sick the day before i0coins launched (and still a little sick ).  Was lying in bed propped up with pillows and on my netbook for a few hours to fork the code .  It paid for the few days of work I missed.

Never gonna let you down

No, he's just one of the people who can't stand that I openly admitted that I had no faith in i0coin doing anything other than mimic ixcoin's rise and collapse, just at an accelerated pace due to publicity.  Apparently admitting that I was only in it for the money is somehow wrong, even though that's the only reason anybody mined i0coins in the first place.

I just did the smart thing.  Instead of watch my pool lose 300 GH/s for a few days and lose out on that money, I made a pool for those i0coin gold rush miners to use so I could offset my losses, or make some extra BTC if the exchange rates were in my favor at the start.

Had an approximately 2 second block solve, US West didn't catch it in time.  I updated the aggression for server sync'ing already, but it still has a 5 second pause if a sync fails.  Since the round was so short, US West ended up sync'ing after the round was already over.  As usual, if a server shows 0 shares during a round, the calculation script stops for manual inspection in case something really bad happened.  When I woke up, I forced it to calculate the round and it caught up with the backlog after a few minutes.

Yup.  Too bad my latency is 60 because I run the servers at actual datacenters instead of my house.  Oh well, I'll keep that in mind for the next lolcoin.

The coins go to my wallet, I just give them an IOU .  I've just been nice enough to honor those IOUs.

6291..less invalids which I'm too lazy to query a count of.