Topic: [ANN] [USDe] Unitary Status Dollar eCoin $$ IMPROVED Halving | KGW Fix Update!!! - page 461. (Read 578463 times)
January 13, 2014, 08:11:45 AM
WTB 100k
January 13, 2014, 07:58:16 AM
What is current web hashrate?
about 500MH seems to be growing quite a bit, wonder why people are flocking to this coin? what is exactly good about it?
Very catchy name, nice block rewards bonuses, good support and promotion.
It can go to cryptsy soon.
January 13, 2014, 07:55:38 AM
What is current web hashrate?
about 500MH seems to be growing quite a bit, wonder why people are flocking to this coin? what is exactly good about it?
January 13, 2014, 07:45:31 AM
Coinarmy is not updating. What the fuck?
Scam? Or just lack of update?
Scam? Or just lack of update?
January 13, 2014, 07:41:46 AM
Is the coin really THAT dawn important for you all to piss and shit all over pooligans??
January 13, 2014, 07:35:51 AM
Also check transactions, I'm willing to bet I'm not the only one who got their coins jacked from coin army last night. He's been doing this with any popular coin\pool it seems.
January 13, 2014, 07:33:57 AM
We have sorted out the issue with the findblock and payout cronjobs ( Mentioned earlier in https://bitcointalksearch.org/topic/m.4483683 ).
All is back to normal.
We are currently storing 214K usde for users who have not set a payout address yet.
Please make sure to claim your coins!
Happy hashing!
SteadyMining.com Team
All is back to normal.
We are currently storing 214K usde for users who have not set a payout address yet.
Please make sure to claim your coins!
Happy hashing!
SteadyMining.com Team
January 13, 2014, 07:31:43 AM
See this thread https://bitcointalksearch.org/topic/pickaxe-pool-scammers-413551
I got jacked at Coin army's pool last night. Never use pickaxe's pool, he is nothing but a scammer. He stole 3815 usde's from me last night.
I got jacked at Coin army's pool last night. Never use pickaxe's pool, he is nothing but a scammer. He stole 3815 usde's from me last night.
January 13, 2014, 07:27:16 AM
WTS 135k
January 13, 2014, 07:26:13 AM
Mined for 45 minutes at coinarmy with 3MH/s and not a single unconfirmed coin.
Is that normal ? Any delay ?
Peeps, just use P2Pool nodes to mine. At least you know they won't scam you. Is that normal ? Any delay ?
January 13, 2014, 07:24:48 AM
What is current web hashrate?
January 13, 2014, 07:22:17 AM
Is there need for a stable pool from us ? (http://poolerino.com)
Yes, it definitely sounds like we could use one. Thanks so much for offering!
January 13, 2014, 07:20:18 AM
Mined for 45 minutes at coinarmy with 3MH/s and not a single unconfirmed coin.
Is that normal ? Any delay ?
Is that normal ? Any delay ?
you're not the only one, all of us mining in coinarmy having same issue i think sad we still mining even there's an issue, hope someone form the pool operator response to their miner, or made some announcement.
January 13, 2014, 07:12:59 AM
Mined for 45 minutes at coinarmy with 3MH/s and not a single unconfirmed coin.
Is that normal ? Any delay ?
Is that normal ? Any delay ?
January 13, 2014, 07:12:05 AM
In my wallet there is a connection with the network, but sync is not. In the config file is written:
addnode=23.253.71.56
addnode=192.237.223.87
addnode=usde.steadymining.com
What to do?
addnode=23.253.71.56
addnode=192.237.223.87
addnode=usde.steadymining.com
What to do?
January 13, 2014, 06:52:13 AM
Is there need for a stable pool from us ? (http://poolerino.com)
January 13, 2014, 06:49:23 AM
steadymining hasn't found a block in 6hrs. lol
Yeah, since CoinArmy seems to be down for me and Pooligans hasn't paid out yet, I'm going to stick with SteadyMining and hope it's just a cron issue.
Thanks for sticking with Steadymining. One of the cronjobs failed while sleeping. We are currently investigating.
Update: ( MPOS issue: https://github.com/TheSerapher/php-mpos/issues/392 affected us <-- originally caused by a worker submitting millions of "Old" shares for a block that was already handled )
All previous blocks that were succesfully submitted onto the blockchain are being processed right now - and users are being credited accordingly. No losses, except for a couple of hours of stats.
January 13, 2014, 06:48:00 AM
Whats the deal with the coinarmy pool at the moment? I have had my miners (1.5+Mh/s) hashing away there all morning and I don't even have a single coin, even unconfirmed. Is it time to move on or will my work be credited in the near future?
January 13, 2014, 06:28:39 AM
2nd Update from usde.pooligans.com
After a very busy night and knee deep is DB-issues, we are finally back in business. We suspect that one cronjob was overloaded and crashed, due to the excessive ammount of blocks found. To not make everything worse we were forced to block access to the stratum server to allow the pool to catch up.
Manually fixing a lot of DB-records and re-running the cronjobs a couple of hundred times finally made the pool catch up. At the moment everything is running normally again, and we are finding blocks and paying out.
All blocks are now accounted for and payed out
Again, we are really sorry about the issues! Dedicated and powerfull hardware on site was performing perfectly, and load on the clusters was not the issue. We did however max out our bandwidth a few minutes after start. We will be sure to make more bandwidt available for the next coin release. This was absolutely a learning experience, and it brought out some good ideas on how to better optimize the pool setup in the future for excessive loads like this.
We have also removed tx-fee and mining fee for everyone.
-The Pooligans Team
After a very busy night and knee deep is DB-issues, we are finally back in business. We suspect that one cronjob was overloaded and crashed, due to the excessive ammount of blocks found. To not make everything worse we were forced to block access to the stratum server to allow the pool to catch up.
Manually fixing a lot of DB-records and re-running the cronjobs a couple of hundred times finally made the pool catch up. At the moment everything is running normally again, and we are finding blocks and paying out.
All blocks are now accounted for and payed out
Again, we are really sorry about the issues! Dedicated and powerfull hardware on site was performing perfectly, and load on the clusters was not the issue. We did however max out our bandwidth a few minutes after start. We will be sure to make more bandwidt available for the next coin release. This was absolutely a learning experience, and it brought out some good ideas on how to better optimize the pool setup in the future for excessive loads like this.
We have also removed tx-fee and mining fee for everyone.
-The Pooligans Team
Pooligans gave me all my coins so no problems there.
January 13, 2014, 06:27:43 AM
2nd Update from usde.pooligans.com
After a very busy night and knee deep is DB-issues, we are finally back in business. We suspect that one cronjob was overloaded and crashed, due to the excessive ammount of blocks found. To not make everything worse we were forced to block access to the stratum server to allow the pool to catch up.
Manually fixing a lot of DB-records and re-running the cronjobs a couple of hundred times finally made the pool catch up. At the moment everything is running normally again, and we are finding blocks and paying out.
All blocks are now accounted for and payed out
Again, we are really sorry about the issues! Dedicated and powerfull hardware on site was performing perfectly, and load on the clusters was not the issue. We did however max out our bandwidth a few minutes after start. We will be sure to make more bandwidt available for the next coin release. This was absolutely a learning experience, and it brought out some good ideas on how to better optimize the pool setup in the future for excessive loads like this.
We have also removed tx-fee and mining fee for everyone.
-The Pooligans Team
After a very busy night and knee deep is DB-issues, we are finally back in business. We suspect that one cronjob was overloaded and crashed, due to the excessive ammount of blocks found. To not make everything worse we were forced to block access to the stratum server to allow the pool to catch up.
Manually fixing a lot of DB-records and re-running the cronjobs a couple of hundred times finally made the pool catch up. At the moment everything is running normally again, and we are finding blocks and paying out.
All blocks are now accounted for and payed out
Again, we are really sorry about the issues! Dedicated and powerfull hardware on site was performing perfectly, and load on the clusters was not the issue. We did however max out our bandwidth a few minutes after start. We will be sure to make more bandwidt available for the next coin release. This was absolutely a learning experience, and it brought out some good ideas on how to better optimize the pool setup in the future for excessive loads like this.
We have also removed tx-fee and mining fee for everyone.
-The Pooligans Team
Jump to: