|
edric
|
 |
June 01, 2014, 08:14:23 PM |
|
It keeps happening, even on a .004 diff block. Something is not cool. Then, by the time that nasty block is knocked out and the crons run and pick it up, we've solved 2 regular blocks in between the minute cron runs. So yeah.
I'll be investigating a little more thoroughly later on today. Have a few errands to run.
|
|
|
|
|
|
|
|
|
|
|
|
|
The forum was founded in 2009 by Satoshi and Sirius. It replaced a
SourceForge forum.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
GWCalvert
|
|
June 01, 2014, 08:22:00 PM |
|
Just as I made that last post I actually looked... We're over 6000% on a .03 diff block, that shouldn't happen! Network hashrate is lower than pool hashrate! Not good!
If this block keeps up like this I'll point my 2mh at it and see if I can blast it out.
Need to get a local wallet to mine to for when this happens, also to watch block numbers across different clients.
Edit: something is definitely odd here.. The wallet is reporting diff of .03~, I wonder if MPOS will be reporting a different number after this block gets blasted off.. I've got some of my hashes on it.
Edit again: MPOS is reporting last block found is 34672, reporting current block we're working on is 34672... TeslaX3 started doing the same exact thing before. I think it may be a problem with MPOS, because with Denarius we find blocks so fast, like sometimes 2 seconds apart.
I'll report back when I know more.
I just moved one of my workers over to the hardcore pool to see if spreading the hash rate around may help stabilize things. I did this a couple of nights ago and it seemed to make the diff behave better. I wasn't awake when my rent-a-miner came online this morning or I would have switched over sooner, as there was virtually no hash power over there. I think the main issue is that we need more hash power steadily across the entire network and that would make things even out. Right now if someone comes online with a big asic unit and drives the diff up and then drops out, it throws the whole network out of whack until the high diff block is solved. |
|
|
|
|
NRPatten
|
|
June 02, 2014, 02:51:16 PM
Last edit: June 03, 2014, 01:34:59 AM by NRPatten |
|
I setup a "abe Block Explorer", Still in testing but seems to work well better than the other one anyway  edit domain change: http://abe.denarius.info/chain/.Denarius |
|
|
|
|
compumine
|
|
June 02, 2014, 05:11:45 PM |
|
I mined this coin from first day a pool was available. But 2 weeks ago, I stopped. I realized that there was something not right with difficulty/coin per 24h. I'm not technical but at the time, the reply I got that I should just keep on mining because difficulty is still low.
Please have a look at that issue as I would like to mine this coin again.
|
*Image Removed*
|
|
|
|
GWCalvert
|
|
June 02, 2014, 06:58:33 PM |
|
I mined this coin from first day a pool was available. But 2 weeks ago, I stopped. I realized that there was something not right with difficulty/coin per 24h. I'm not technical but at the time, the reply I got that I should just keep on mining because difficulty is still low.
Please have a look at that issue as I would like to mine this coin again.
I believe that KGW is actually working right, but with a low network hash rate when a large amount of hash power is added quickly, you see a huge spike in the diff level. The reverse is also true, in that the higher hash rate keeps the difficulty higher and when a large amount of hash power drops out, the network is left with relatively low hash power to solve the difficult block. This can cause huge delays (stalls) in the block chain where nothing can be confirmed because no blocks are being solved. For example: say the network hash rate is 5Mh/s and someone joins the network with a 30 Mh/s unit. When the next block is found KGW sees a 700% increase in the network hash rate and causes the difficulty level to spike. If that same person drops off with his 30Mh/s unit, KGW does not see the drop in the network hash rate until that higher difficulty block is solved. Whereas, say you have a network hash rate of 300 Mh/s and a 30 Mh/s user pops in and out, there is not that much of a noticeable difference, ~10%, so the chain keeps on moving along with only a slight delay (a few seconds or so max) in finding the next block. The best solution to getting a stable block chain (no matter what re-targeting method is being used) is to have a high network hash rate. Having a low hash rate not only creates wild swings in the difficulty, but also makes the entire network more vulnerable. I have added a small amount of hash power to network the past few days and it has become much more stable, but there are still occasional delays of 30 minutes or so at times. |
|
|
|
Nthused (OP)
Legendary
 Offline
Activity: 1554
Merit: 1001
|
|
June 04, 2014, 06:42:50 PM |
|
I'm glad you are all seeing what I am seeing, it might have something to do with how the Wallet gets the Estimated Network Hashrate and is Deciding difficulty upon that when it isn't correct e.g Pool hashrate 10mh/s, Net hashrate is way under or over Combined pools Hashrate at times, with only the pools solving the blocks anyway.
If anyone want's to have a crack at fixing it/Implementing a Different Difficulty Adjustment, I'm all for it as a 0.1 BTC Bounty will be offered if you succeed.
|
|
|
|
|
|
NRPatten
|
|
June 05, 2014, 09:30:10 AM |
|
I'm glad you are all seeing what I am seeing, it might have something to do with how the Wallet gets the Estimated Network Hashrate and is Deciding difficulty upon that when it isn't correct e.g Pool hashrate 10mh/s, Net hashrate is way under or over Combined pools Hashrate at times, with only the pools solving the blocks anyway.
If anyone want's to have a crack at fixing it/Implementing a Different Difficulty Adjustment, I'm all for it as a 0.1 BTC Bounty will be offered if you succeed.
I sent you a pm not sure if it will work but worth a look |
|
|
|
ice777
Member
Offline
Activity: 60
Merit: 10
|
|
June 05, 2014, 09:57:23 AM |
|
WTF with this shit coin without any innovation
|
|
|
|
|
|
NRPatten
|
|
June 05, 2014, 10:11:47 AM |
|
@Nthused ok i just compiled the coin with Digishield, I have not started the coind i just built it to make sure it would build..
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3458
Merit: 1126
|
|
June 05, 2014, 06:01:01 PM |
|
@Nthused ok i just compiled the coin with Digishield, I have not started the coind i just built it to make sure it would build..
Do you have a set of instructions for implementing DigiShield? |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
|
|
|
edric
|
|
June 06, 2014, 04:08:36 AM |
|
My pool has been updated, was in a hurry so I just kinda did a ninja update, sorry for everyone getting disconnected with no notice. It's been one of those days
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3458
Merit: 1126
|
|
June 06, 2014, 04:18:49 AM |
|
Come get your DRS! WALLET UPDATED! http://www.hasher.caPROP reward system Worker Stats DDoS Protected High Performance Backend Simple setup and usage Auto ProfitPorts (beta testing now) To mine: Username: your DRS wallet address OR Global Key (ProfitPorts) Password: anything DRS (vardiff): stratum+tcp://stratum.hasher.ca:3554 DRS go straight to your wallet once the block is confirmed. We don't hold your DRS! Cheers and Happy Hashing! |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
Nthused (OP)
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
June 06, 2014, 05:17:18 AM |
|
The majority of the pools updated which is a good thing as well as a Block Explorer & Hi-Lo Game. Everything is set for smooth sailing for the miners  DRS Giveaway Ongoing Indefinitely |
|
|
|
|
|
NRPatten
|
|
June 06, 2014, 06:12:27 AM |
|
My pool has been updated, was in a hurry so I just kinda did a ninja update, sorry for everyone getting disconnected with no notice. It's been one of those days
You don't have to shutdown Stratum for a coind update just disable the crons, wait for the current cronjobs to finish, stop coind and restart new coind enable crons ( Do this as fast as you can and the pool will be fine. ) |
|
|
|
GrinZ
Legendary
Offline
Activity: 1572
Merit: 1002
|
|
June 06, 2014, 07:12:41 AM |
|
|
|
|
|
|
Nthused (OP)
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
June 06, 2014, 07:55:55 AM |
|
Thanks Mate, Donated to Faucet  |
|
|
|
|
Nthused (OP)
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
June 06, 2014, 02:30:58 PM |
|
Switchover worked a Treat, Denarius is back to Normal and Stable now, No more Crazy weird KGW Difficulty Adjustments and showing True Nethashrate now.
|
|
|
|
|
|
edric
|
|
June 06, 2014, 03:38:50 PM |
|
My pool has been updated, was in a hurry so I just kinda did a ninja update, sorry for everyone getting disconnected with no notice. It's been one of those days
You don't have to shutdown Stratum for a coind update just disable the crons, wait for the current cronjobs to finish, stop coind and restart new coind enable crons ( Do this as fast as you can and the pool will be fine. ) I know, usually that isn't a problem but I had a couple of hiccups so it became necessary. Usually upgrades are painless and only take a few seconds, seems like everything is the hard way lately. |
|
|
|
|
GWCalvert
|
|
June 06, 2014, 10:29:11 PM |
|
I see hashing at all 4 listed pools today. Good job, everyone! Now we just need to get some more people interested. I'll try to help where I can.
|
|
|
|
|
