About the Nethash problem.
Could it be possible that the pool shows the
poolhash as the sum of all the hashrates
< 10 And the pool shows the
nethash as the
actual hash being thrown at the pool, so also people (as OCminer mentioned .. retards) that mine with 1 GH and only get 10MH
Cause the nethash was 10GH a few times when Maximiner was finding twice as much blocks.
Or am I just being stupid?
Damn you're absolutely right.. Why did I not think of this ! Yes sure ! There you see which "overhead" we have !
Are you being sarcastic? Cause I'm a total nono how pools work lol.
Nope you're right, I was just not thinking of it at the first place.
This also explains the rising diff.. As the guys are pumping more and more MH/s into the network, blocks are found much more early (on the pool where those guys pump in the extra hash) and so is the diff rising.
That would make a LOT of sense!
In my experience with this launch, tuning my hash to be just under 10Mh (seems to average between 8.5 and 9.5), but I am seeing swings of extreme of anywhere between 6 and 11.5, along with a pretty good return in coin. Now if we can just repair the panic damage from last night and pull the value back to where it belongs, this launch will be a real winner!
OCMiner,
From your posts, it seems you had a lot to do with the pool regulation. After today's Multicoin launch fiasco, I was wondering how hard it would be to set up another launch like this one for that dev team. As it is, I don't trust them as far as I can throw them and will not be participating in a relaunch of that coin tomorrow. But if they were to step back a few days and do a truly fair distributed launch like this one or MIN, that would go a long way to restoring my faith in that team. I mentioned the MIN and RVC launches in their "re-launch" thread, and for one, hope that they might contact you and inquire about it and your services. While I am not a big fan of not having a POW wallet, I really like the results in distribution and difficulty this format has produced, and I hope to see a LOT more of it in the future!
Good Job!
First - Thanks for your props, I appreciate.
When the dev contacted me for this project, the whole "job" did not sounded too special.. Be part of a pool network which regulate their pools on their own, just don't release the source to the public and cap the speed to 10 MH/s per user and do a one Account per IP Limit.
After I said "yes" it became clear that I was the only one who will be doing the coding stuff - put in the speed limit at the pool - as no other "big" pool wanted to touch the coin.. I'm not sure why, but this postponed the launch a few days since I had to do everything on my own and much testing was needed - you cannot simply test "in wildlife"
While testing and coding, I've wrote RefrigeratorCoin as no other X15 PoW/PoS was available during that time (they basically all ended PoW while I started working with them
). It turned out that the whole pool thing was harder than I thought as there were so many variables with the stratum and pool software frontend ... See the spikes in network for example now.. Even though I'm banning rigs which are faster than 10.24 MH/s for 60 seconds, those guys simply don't care about it and continue hashing.. They are probably renting hash and are not seeing that their rigs are getting banned every 3 minutes for 1 minute :-)
A "normal" coin release, like the MultiCoin Team could have done earlier this evening, is really straightforward and simple:
0. Get your seednode(s) ready (minimum two vps with the wallet online) and synchronized.
1. Upload Source to a private github repo
2. Upload Wallets to Mega
3. Save those links in the bitcointalk.org thread and push on "
Preview" instead of post - hold that post on a tab in your browser until launch.
4. @ Launchtime simply switch the Github-Repo to public and push on "Post" @ bitcointalk.org
5. Look how Shadow_Runner is raping the first block out of the wallet :-)
Thats it for the coin dev .. He's basically done here.
The Pool OP now has a shitload of work todo.. Download the wallet fast into a separate VM on the server and compile it there - watching for errors the dev might have done, missing "chmod"'s, missing obj directories etc. Look for potential securities issues with the wallet, does it open any suspicious connections when running it ? Does it only listen on the ports it is supposed to ?
After that, starting stratum and getting the Cronjobs running is pretty straightforward ...
For me, a "failed launch" of a "normal" coin - no new algo, no speedlimit, no quirks is
almost unforgiveable - there is simply nothing that can fail - it is a cloned wallet:
1. Clone it
2. Make new Genesis Block
3. Run it and see that Diff Adjustments are working, coin reward matches your setting etc.
4. Create new Genesis Block again and release to the public..
However to come to the point:
You saw all my posts in this thread, I think I'm on every page here, some people already thought I'm the Dev of this coin :-)
I had like a week before release to get things running with speed limit, stratum etc. (no i did not had the source, i wrote my own)
Currently I'm a bit exhausted and would step back from another launch in short time - but at the end - after maybe one or two weeks - yes - it was fun and I would do it again if a decent Dev Team would step up to me, this is what Cryptoenthusiasm is all about :-)
