A quick announcement- We've completed the migration of the KarmaCoin pool to one of our faster SSD-equipped servers. You should see better efficiency as well as a much, much more responsive frontend now.  |
|
|
|
Nice to see that pool admin run off with our coins. REAL NICE!
We have not run off with anyone's coins. I can only assume you're referring to the LeafCoin pool, which we shut down for mining due to massive block chain forks that caused lost coins. This already happened twice with the coin, and it is just not worth the hassle and lost money out of our own pockets due to problems with the coin itself. You can also follow the directions above and I'll try and sort out payment for your mining time out of our own coins. Personally I'd suggest you look at other coins to mine instead of Leaf moving forward, I don't have much faith in it. Additionally, it would seem that there is 0 progression in the updating of blocks in the SynCoin Pool and therefore no coins can mature and be confirmed. A swift response would be greatly appreciated. --Zer0Evasi0n I haven't checked on the syncoin pool in weeks since it was essentially dead... but I just restarted the wallet, you should be able to withdraw shortly once the block chain catches up. coins will mature and be confirmed by people mining on other pools. Withdrawals don't require active mining on the pool to be processed as long as *someone* is mining on the blockchain (which it seems like barely anybody is, the difficulty is 0.03 right now.) |
|
|
|
Nice to see that pool admin run off with our coins. REAL NICE!
We have not run off with anyone's coins. I can only assume you're referring to the LeafCoin pool, which we shut down for mining due to massive block chain forks that caused lost coins. This already happened twice with the coin, and it is just not worth the hassle and lost money out of our own pockets due to problems with the coin itself. You can also follow the directions above and I'll try and sort out payment for your mining time out of our own coins. Personally I'd suggest you look at other coins to mine instead of Leaf moving forward, I don't have much faith in it. |
|
|
|
Im trying withdraw my Zeitcoin coins since last week in zeit.hashstrike.com and no transfer my coins.!!I sended email,but no answer...
I apologize for the delays. Due to work obligations at my day job, I haven't had time to manage the support ticket system over the past few days. I've re-run all the manual payouts for Zeit and you should have received your coins. If you have not received them yet, please either PM me or email directly to hashstrike at gmail dot com and I'll help you out. Moving forward, I'll most likely be shutting down the existing pools for mining with the exception of the KarmaCoin pool. ALL pool pages will remain up for withdrawals for the forseeable future. |
|
|
|
So what happened to the Karma pool?
It's back up now. There was a memory issue that caused a mysql crash, so everything needed to be restarted. |
|
|
|
this 21btc buy wall is pissing me off  i wanna buy at 1sat and then it must shoot up to 10 hahah sigh This! and FYI, we're looking into an issue with payouts, it should be resolved shortly. Thank you!
Payouts are running again! please implement worker disconnect algorithm to maintain sub 30% network hashrate This too would be really great. Would need to average out the net hashrate over a period of time ofcourse though, net rates fluctuate so much for all the reasons I'm quite sure you know The bigger problem is that no other pools are even advertising in the thread here! They should be doing more to put themselves in front. It's tough when we not only have to handle the maintenance of our pool, but also add code to make it smaller? As for any risks of a fork, there's an exceedingly low chance of this happening. I think people are scared of what happened with DogeCoin, but that was specifically due to some bugs in the wallet code that made the fork survive. Half the pools/exchanges were on one wallet, and the other half were on another. We'll continue to monitor things, and if we see anything dangerous happening then we'll shut off a couple of our stratum servers temporarily to bounce people to other pools. That's the easiest way, since writing our own worker banning algorithm would take a LOT of work. |
|
|
|
FYI, we're looking into an issue with payouts, it should be resolved shortly. Thank you!
Payouts are running again! |
|
|
|
|
FYI, we're looking into an issue with payouts, it should be resolved shortly. Thank you!
|
|
|
|
But when I send coins, I get this strange message: ~/zeitcoin/zeitcoind sendtoaddress MYHsWpJJ34NewErMxtrWT4EaqJTiWkFUHY 50000 starterkit starterkit
error: {"code":-4,"message":"Error: The transaction was rejected.
This might happen if some of the coins in your wallet were already spent,
such as if you used a copy of wallet.dat and coins were spent in the copy
but not marked as spent here."} Which is not what I did. Please help me liberate my coins! They are stuck somewhere, but where? What can I do? It sounds like your copy of the blockchain is corrupted. Try these steps: - zeitcoind stop - Backup a copy of your wallet.dat - Go to your .Zeitcoin folder, and delete everything EXCEPT wallet.dat and Zeitcoin.conf - start zeitcoind It will take a long time to re-download the blockchain but that should fix it. -rescan only checks your copy of the blockchain on disk, and it sounds like yours is wrong for some reason, which is really weird. Thanks a lot. I had already tried that, but hey - I am trying it again. And actually downloaded the sources anew, and compiled again, because I thought perhaps the wallet was updated in between? Superb results :-) ---> Zeitcoin: Warning: error reading wallet.dat!
All keys read correctly, but transaction data
or address book entries might be missing or incorrect.
************************
EXCEPTION: St13runtime_error
ReserveKeyFromKeyPool() : read failed
Zeitcoin in ThreadStakeMinter()
terminate called after throwing an instance of 'std::runtime_error'
what(): ReserveKeyFromKeyPool() : read failed
[1]+ Aborted zeitcoin/zeitcoind
ooops. WHAT is that? Fortunately, I had kept the old binary ( March 5th) And that one started without problems. Downloading the blockchain now... You can also try starting it with -salvagewallet (if you haven't tried that already). It will keep your keys but delete all transaction data out of the wallet. |
|
|
|
Anyone else getting double their hashrate on morecoins?? the pools acting odd. I have there 890kh/s It seems to be ok now.. getting 1.2MH/s but a while ago i was getting 2.8MH/s which is impossible on my hardware. Any time you see your hash rate on a pool page, remember that it is JUST an estimate. It is guessing based on how fast you are sending shares. And if a pool has their stats set to update quickly (like every minute) then you can hit spots where you send a ton of shares quickly and it makes it look like your hash rate is much higher than it actually is. The other extreme is that you can see half or less of your real hash rate. This is also affected by vardiff, until the size of shares you submit stabilizes. tl;dr- don't be concerned in the short term if your hash rate is wrong. Give it time to stabilize! |
|
|
|
But when I send coins, I get this strange message: ~/zeitcoin/zeitcoind sendtoaddress MYHsWpJJ34NewErMxtrWT4EaqJTiWkFUHY 50000 starterkit starterkit
error: {"code":-4,"message":"Error: The transaction was rejected.
This might happen if some of the coins in your wallet were already spent,
such as if you used a copy of wallet.dat and coins were spent in the copy
but not marked as spent here."} Which is not what I did. Please help me liberate my coins! They are stuck somewhere, but where? What can I do? It sounds like your copy of the blockchain is corrupted. Try these steps: - zeitcoind stop - Backup a copy of your wallet.dat - Go to your .Zeitcoin folder, and delete everything EXCEPT wallet.dat and Zeitcoin.conf - start zeitcoind It will take a long time to re-download the blockchain but that should fix it. -rescan only checks your copy of the blockchain on disk, and it sounds like yours is wrong for some reason, which is really weird. |
|
|
|
Hashstrike must raise fee to 3 or 4% it would be good motivation
I'd prefer if they just emailed all the miners on it. Likely a lot will just be pointing there and not checking in here or there to know of the problem or that their fees have gone up. Increasing fees only works if people know they've gone up. I'll send out an email later today if we stay over 50% for an extended time again. I'm not worried about the effect of multi-pools, because our hash rate went up at the exact same time as the net hash rate did... which means that our users are following what the multi-pools do. I seriously doubt we'll be 80% when the multi-pools leave because we'll lose users too. |
|
|
|
The boyz at zeit.morecoins.org could do with a few more hash-helpers, they've been stuck on a block for days - I've chucked in my 1.3 Mh/s but they could still do with a few more Megz, just to get them going again. Lets show the rest that 'community spirit' actually MEANS something with ZeitCoin! Guess not. Active miner @ hashstrike has increase by almost 100 since I first made this post. This is the problem, they're crunching almost all the blocks leaving the other pools running dry so people are switching across to hashstrike. In the last 20 blocks hashstrike's solved 7 blocks in a row, that's REALLY bad for a coin that only requires 4 confirmations per transaction. Come on people, if you go to Hashstrike you're going to dent the confidence in the coin, the price and interest will suffer as a consequence of this. You're contributing to the demise of the coin you're so desperate to get! Yep, noticed that Registrations are now closed and pool fees are 2%. |
|
|
|
The boyz at zeit.morecoins.org could do with a few more hash-helpers, they've been stuck on a block for days - I've chucked in my 1.3 Mh/s but they could still do with a few more Megz, just to get them going again. Lets show the rest that 'community spirit' actually MEANS something with ZeitCoin! I'll also recommend http://zeit.imine.at/, I've spoken to the admin (evoked) a bunch of times and he is a great guy |
|
|
|
Need some folks to move away from HashStrike. That pool's pushing almost 50% of the hashes currently which is not good.
Please spread out the hashing more folks
Indeed If it continues like this we will be closing registrations and raising fees slightly to encourage people to spread out their hashes a bit more. |
|
|
|
PAYOUT SYSTEM MOVED BACK TO PPLNS! Why the payout change?  ? Please read the news item for a full explanation. PPLNS is a good thing for miners! It makes for more steady payouts (especially with a random block reward coin). We only switched to PPS because of pool load issues, so we were long overdue for switching back. |
|
|
|
CAUTION Pool http://zeit.hashstrike.com/ not pay money. I've been waiting 24 hours to pay nothing. I wrote them two emails and no response. I'm going to benefit elsewhere Hashstrike always pays me correctly. Been with hashstrike since ZEIT was launched. Always been smooth and correct. Thank you for the support guys. Petreff- It looks like you deleted your post but I went and researched it anyways.. we did miss your support emails, and I'm sorry for that  I'm not showing any failed payouts though. I will contact you to sort it out. |
|
|
|
Somebody else have another problem with HashStrike? Suddenly transactions only show up as a fraction of usual transaction. For example instead being credited for a round 2,000 ZEIT, I am getting credited 20 to 100. You can only back trace the transactions for the last half hour.
On the left side in the dashboard panel you can see your hourly rate. So instead the usual 150,000 ZEIT it shows around 3,000 ZEIT.
Somebody got Hashstrike respond to that? I already sent also a support email. Hopefully they can fix their problem soon.
I figured out the problem.... the PPS system failed back to a default block reward of 10,000 coins when it couldn't properly figure out the average of the last few blocks. This happened for the last 40 blocks or so, I'm looking for a good way to go back through and reset payouts for these. Don't worry, everyone will get paid their fair share! Thanks for the speedy reply. Good Support! Some more technical details, here's what it looks like in our logs. There were 55 blocks that got paid out at the wrong amount. As you can see now at the very bottom, it's showing the proper average again. I'll be putting in individual manual payouts for everyone who mined during those blocks using an average value of 379,000, since that is the highest numer that has showed up recently. You should see an extra Credit_PPS show up in your transactions with the missing amount soon. 2014-03-12 16:14:01 - INFO --> PPS reward using block average, amount: 333363 difficulty: 14.34074064
2014-03-12 16:16:03 - INFO --> PPS reward using block average, amount: 337727 difficulty: 13.58182264
2014-03-12 16:18:02 - INFO --> PPS reward using block average, amount: 338696 difficulty: 11.77683418
2014-03-12 16:20:04 - INFO --> PPS reward using block average, amount: 336236 difficulty: 13.91693288
2014-03-12 16:22:02 - INFO --> PPS reward using block average, amount: 362580 difficulty: 15.73699633
2014-03-12 16:24:02 - INFO --> PPS reward using block average, amount: 378656 difficulty: 15.34110891
2014-03-12 16:26:34 - INFO --> PPS value (Default): 10000
2014-03-12 16:28:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:30:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:32:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:34:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:36:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:38:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:39:37 - INFO --> PPS value (Default): 10000
2014-03-12 16:44:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:46:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:48:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:50:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:52:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:54:02 - INFO --> PPS value (Default): 10000
2014-03-12 16:56:01 - INFO --> PPS value (Default): 10000
2014-03-12 16:57:39 - INFO --> PPS value (Default): 10000
2014-03-12 17:02:38 - INFO --> PPS value (Default): 10000
2014-03-12 17:06:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:08:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:08:35 - INFO --> PPS value (Default): 10000
2014-03-12 17:10:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:10:24 - INFO --> PPS value (Default): 10000
2014-03-12 17:12:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:14:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:14:44 - INFO --> PPS value (Default): 10000
2014-03-12 17:17:07 - INFO --> PPS value (Default): 10000
2014-03-12 17:17:52 - INFO --> PPS value (Default): 10000
2014-03-12 17:18:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:18:20 - INFO --> PPS value (Default): 10000
2014-03-12 17:18:51 - INFO --> PPS value (Default): 10000
2014-03-12 17:19:07 - INFO --> PPS value (Default): 10000
2014-03-12 17:19:29 - INFO --> PPS value (Default): 10000
2014-03-12 17:19:59 - INFO --> PPS value (Default): 10000
2014-03-12 17:20:22 - INFO --> PPS value (Default): 10000
2014-03-12 17:22:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:22:15 - INFO --> PPS value (Default): 10000
2014-03-12 17:24:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:26:03 - INFO --> PPS value (Default): 10000
2014-03-12 17:27:24 - INFO --> PPS value (Default): 10000
2014-03-12 17:28:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:30:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:32:01 - INFO --> PPS value (Default): 10000
2014-03-12 17:34:03 - INFO --> PPS value (Default): 10000
2014-03-12 17:36:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:38:03 - INFO --> PPS value (Default): 10000
2014-03-12 17:40:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:42:03 - INFO --> PPS value (Default): 10000
2014-03-12 17:44:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:46:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:48:03 - INFO --> PPS value (Default): 10000
2014-03-12 17:50:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:52:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:54:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:56:02 - INFO --> PPS value (Default): 10000
2014-03-12 17:58:02 - INFO --> PPS value (Default): 10000
2014-03-12 18:17:59 - INFO --> PPS reward using block average, amount: 349542 difficulty: 14.26836705
|
|
|
|
|
Show Posts
