CLEANWATER, WHY WAS 600 BLOCKS INSTAMINED BEFORE THE LAUNCH! I HAS EVERYTHING READY TO GO STARTED MINING 3 MINTUES AFTER LAUNCH AND THE BLOCKS WERE WHIZZING BY. EXPLAIN.
WE WILL NOT STOP FROM BRINGING THIS UP
IPO!!!!
The first block was 10m coins for the IPO coins, and the next 50 were 1 coin payout, to confirm the first block. I made the first 55 blocks as 1 coin to give a buffer in case I couldn't stop in time. (first blocks fly by, even with just a CPU) I got distracted with some edits and I stopped *at* block 56. So, I guess I instamined a single block, but it was an accident.
We were assisting a couple other pools (can verify with IRC logs) at launch, and I hadn't even had time to start up my own miners. We had the official pool down for the first few minutes at launch so the hashrate would spread around, without us causing a fork. The diff started low, and we got way more hashrate than we expected - 1.5gh - so the people who mined early got blocks quickly. Difficulty is adjusting now, and balancing out.
This isn't my coin, I just helped out. It was openly premined for IPO and nobody on the dev team "instamined" except for the 1 extra block of 1k i got by accident. The entire IPO is already sent to the nonprofit org owners, and I'll get a blockchain explorer up by tomorrow or Tuesday at latest, I need some rest.
Thanks
Thank you for the explanation. That is the first I have heard about it.
Although the official pool did not fire up on launch and did not come online until at least 35 mins after the launch. A few other pools were not online until later too. As soon as I realised I switched to hashing.at and immediately started getting accepts, I did manage to scrape in a couple thousand WATER but with the initial pools failing, so much more could have been made.
My fault though I should of had all the pools in my config ready for launch.