I'm pretty impressed. This coin is looking really nice. GJ   UC.DEDICATEDPOOL.COMMining Information- Custom stratum/mpos environment
- Vardiff enabled
- PPNLS payout system
- Everything is transparent - blocks, donations, fees.
Server Infrastructure- SIX(6) SERVERS IN CLUSTER
- DDoS level 7 cloudflare, 5 and 3 stratum, and level at 1 switch level
- 8 Core servers, 256GB DDR3 RAM, RAID 10 SSD
- Ramdisks, memcaches, to make things go extremely quick
|
|
|
|
Hi, I'm an admin from coins4everyone.com.
From what binaryclock at dedicatedpool observed, somebody started mining 2 mn before yesterday's launch, and got something like 30 blocks in those 2mn.
I have not seen any finger pointing about the culprit, but I will...
be pointing to me... that might be my fault. I've checked my log, and it appears that I launched the pool's stratum at :58 instead of :00 (talking about minutes).
So, I might be culprit on that part.
In order to get your paranoia down, I wasn't trying to steal, or to cheat. Our pool is running for quite some time, and we are establishing our reputation with honnesty and dedicated service to our miners and coin dev.
If I was trying to cheat, I would have got 1 block in advance. That's really not worth the reputation. After realizing my error, I was ready to make it up to the dev, by, for example, giving back twice the amount "stealed" to the community.
The reason why the stratum was launched too early is pretty stupid. I usually take my time when compiling a wallet for a launch (to check some stuff, like a hidden obvious trojan, and to be sure that I made no mistake), and I end up starting the wallet 10 mn after the launch. Well.. it appeared that, I was way faster yesterday. When I launched the stratum, I assumed it was around :05 or :10, instead of :58.
As binaryclock also stated, the coin could have survived a 30 block steal (which should have been 1 or 2 blocks) even if it was not fair (and it wasn't), what it didn't survive was the error in the diff adjustement that provoked the instamine of 5% of the whole amount of UVC.
I came clean about that to the dev, just after I had time to analyze my log file this morning, and apologize for the error, but got no answer so far.
I know that people get stressed out during a launch. They get very sensitive. rage, and get their suspicion up very easily.
If you look at it with a little perspective, this wasn't a scam coin, and nobody tried (or at least succeeded) to steal anything.
It was just mistake committed from the dev and a pool admin.
You can rest assured that on my part, that won't happen again.
Cheer's and long live to UVC!
Cheers. Thanks for clearing that up and coming clean. Shit happens. It's how you deal with the problem after the fact that defines the man. BTW, i wasn't worried about the 30 blocks myself. But people were finger pointing to me too so I had to clear the air and say exactly what happened Didn't know who did it or what, just knew 30 blocks were mined before that. http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool  |
|
|
|
whats wrong with cryptocoinz? not finding many blocks..
Everything is fine. Just Dedicated is taken all the blocks  Yea, they are. But it should not make a huge difference what pool you mine at unless they are more than 40-60% of the total network hash. Join us @ http://uPool.co We are finding blocks but could use the extra hashing power If anyone noticed, dedicated pool has 2.4GH/S out of 2.9GH/S hashing power. Please spread your hash!:/ About half of that hash rate is the top 10 users on there as well... Unfortunately this is what happens when some pools at the top of the list have problems at launch. It happens. The good thing here to note is that Dedicated can handle the hash until the other pools get the issues solved. It would be worse if there weren't any pools to handle the hash rate and nobody could mine  |
|
|
|
poolerino is not a success!!!
We, the admins of poolerino.com, are very sorry for what happend. The new coindaemon did not run in the old environment from yesterday. We should have made a clean install, but didnt. So we had to build everything new within last minutes. Again, sorry from us. Mike Poolerino is a good pool. Thanks for the update Mike. See what you can do to fix the issue and get mining again. http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool |
|
|
|
Guys, spread the hash! Unless you want a 51% hash attack. Dedicated is almost @ 51%
I'm serious!  The problem with that is that dedicated would actually have to try to 51% it. We have over 200 connections to our stratum. However I do agree that you guys need to spread it around a bit. |
|
|
|
UC.DEDICATEDPOOL.COMMining Information- Custom stratum/mpos environment
- Vardiff enabled
- PPNLS payout system
- Everything is transparent - blocks, donations, fees.
Server Infrastructure- SIX(6) SERVERS IN CLUSTER
- DDoS level 7 cloudflare, 5 and 3 stratum, and level at 1 switch level
- 8 Core servers, 256GB DDR3 RAM, RAID 10 SSD
- Ramdisks, memcaches, to make things go extremely quick
|
|
|
|
Updates:
We are not here to make excuses. We screwed up, that's on us. More details regarding the specific pool that started early will be made public soon. We're working to get the relaunch up ASAP! All we ask is for your understanding.
You coin daemon started on block 51. I watched someone mining from block 51 to 79ish or so. Dedicated hit its first block at 5pm (+/- 15 seconds) and it was block 82 if I remember correctly. Therefore someone mined from block 51 to 81 (30 blocks). I saw the blocks being mined at least 2 minutes early. However, 30 blocks being mined 2 mins before launch isn't going to kill a launch. It is the difficulty of the coin that failed. Let's stop shifting blame. http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool |
|
|
|
Which pool mined early?
was in dedicated right at launch 17:00, and the block was 75 (my first transaction),
does that mean another pool mined 75 blocks before ?
show your evidence.
I think we can also blame the pool that mined early for the DDoS attacks also. Looks like I may need to get DDoS protection.  You didn't get DDoS'd. You probably got DDoS'd by your own stratum because of the low difficulty of the coin. It happens. Been there, done that. |
|
|
|
You're dif retarget should be dgw, so there won't be instamine, and for god's sake never launch a coin with 0.000002 dif start
Don't let this coin dev blame pools for their incompetence. I am starting to get very upset with the shifting of blame here and won't stand for it. The problem here is the coin dev's fault, nobody elses. |
|
|
|
Which pool mined early?
was in dedicated right at launch 17:00, and the block was 75 (my first transaction),
does that mean another pool mined 75 blocks before ?
show your evidence.
Thank you sir. |
|
|
|
FINAL CONCLUSION/DECISION:
It has been revealed that there was actually no issues with our difficulty re-adjustment and we will be RELAUNCHING SOON! STAY TUNED FOR MORE INFO. A CERTAIN POOL MINED EARLY AND WE HAVE PROOF.
how is this possible? Dedicated Pool has mined 1705 blocks. That would take over a day if diff was readjusting correctly. http://uc.dedicatedpool.com/index.php?page=statistics&action=poolThat's probably the pool that launched early! The pool I joined had only mined 3 blocks. this would mean they found 5% more blocks, not 50,000% more Thank you. Some people are just FUDing like crazy here. The stupidity that I'm reading is insane. |
|
|
|
FINAL CONCLUSION/DECISION:
It has been revealed that there was actually no issues with our difficulty re-adjustment and we will be RELAUNCHING SOON! STAY TUNED FOR MORE INFO. A CERTAIN POOL MINED EARLY AND WE HAVE PROOF.
how is this possible? Dedicated Pool has mined 1705 blocks. That would take over a day if diff was readjusting correctly. http://uc.dedicatedpool.com/index.php?page=statistics&action=poolThat's probably the pool that launched early! The pool I joined had only mined 3 blocks. Dedicated launched at 5pm. The server time may be a few seconds off, but it was 5pm. And, diff readjustment as nothing to do with mining "early." The problem is with the code of this coin. |
|
|
|
PUBLIC APOLOGY
We are truly sorry for this inconvenience and are working hard to get this show on the road. If this launch has taught us anything, it is that all it takes is one bad apple to ruin the batch. We have proof there was instamining BEFORE our launch, and we have learned our lesson. We will not proceed if things are not 100% fair for all, therefore, stay tuned for our relaunch announcement. We will try to get it back up ASAP so bear with us.
Once again, thank you all for your understanding and support. This is a long-term project for us, therefore this extra 1 hour that is needed to get things right will not effect our long term objectives.
More info to come very soon.
Sir, I'm not sure what you're getting on about but the real problem is the diff readjustment. No bad apples in a bunch was going to ruin that. Stop trying to shift blame on pools for an obvious oversight and failed difficulty launch. |
|
|
|
FINAL CONCLUSION/DECISION:
It has been revealed that there was actually no issues with our difficulty re-adjustment and we will be RELAUNCHING SOON! STAY TUNED FOR MORE INFO. A CERTAIN POOL MINED EARLY AND WE HAVE PROOF.
how is this possible? Dedicated Pool has mined 1705 blocks. That would take over a day if diff was readjusting correctly. http://uc.dedicatedpool.com/index.php?page=statistics&action=poolIt's because people are just FUDing at this point. Obviously to anyone intelligent his statement makes no sense Of course there was an issue with the diff readjustment!:) |
|
|
|
Where We Went Wrong:
Our difficulty re-adjustment experienced some issues, therefore, instamining occurred. We are sorry for the inconvenience.
What We Have Learned:
Certain pool operators CAN NOT BE TRUSTED.
We will relaunch with our difficulty re-adjustment FIXED and will only be sharing the source with a select few TRUSTED pool operators. Thank you all for your understanding.
Thank you for updating us. I will kill the stratums. http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool |
|
|
|
Gentlemen, Dedicated is still mining until I get a PM or the ANN is changed. Here's what the ann says:
Everyone Please Stay Calm!
We are working to resolve the issues at hand. The giveaways will be delayed until we figure out the best course of action. It seems that a pool did in fact jump the gun and mine early, however most blocks are orphans up until this point, so we are still assessing the situation.
Stay calm, we are working to resolve this. Thank you for your patience.
If the coin is to be relaunched, please change the ann or have the coin dev PM me. Thank you so much, http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool |
|
|
|
LAUNCH FAILED, IDIOTS RELEASED SOURCE 20 min BEFORE LAUNCH.
MINERS SCREWED, 500 blocks mined before wallet password. WTF I did found my first block on block 36 solo, after I got password here .. so stop laying No, he is not lying. SOURCE WAS PUBLISHED 20min before launch. Dedicated pool was working before launch. THIS WAS A JOKEDedicated waited until 5pm exactly (-/+ 10 seconds or so due to different clock times.) I launched when my computer clock said 5pm. Please do not lie. Ask anyone who was mining. http://uc.dedicatedpool.comRyan, dedicatedpool.com support/admin admin@dedicatedpool.com / IRC on freenode ##dedicatedpool |
|
|
|
|
The diff wasn't set correctly on this. Should been updating each block.
|
|
|
|
We will be online at 5pm. (5 minutes from now) UC.DEDICATEDPOOL.COMMining Information- Custom stratum/mpos environment
- Vardiff enabled
- PPNLS payout system
- Everything is transparent - blocks, donations, fees.
Server Infrastructure- SIX(6) SERVERS IN CLUSTER
- DDoS level 7 cloudflare, 5 and 3 stratum, and level at 1 switch level
- 8 Core servers, 256GB DDR3 RAM, RAID 10 SSD
- Ramdisks, memcaches, to make things go extremely quick
|
|
|
|
|
Show Posts
