Topic: [ANN][DRS]Denarius|Scrypt|DGW3|Exchange|Faucets|10 Coin Reward|No Block Halving| - page 13. (Read 53698 times)

We now have a Fixed Denarius coin

Updated Denarius Source: https://github.com/Denarius-/Denarius

Windows Wallet V1.0.1: https://mega.co.nz/#!vUIE1CSI!izzJ7zHJsDjQcUIqw3hnx4_VRCN5BiKLyU7x7Yr3pQA

All Pools, Games, Services, Exchanges Please update to the New Source A.S.A.P before Block 40K

Windows & Mac Wallets with Updated Logo will follow after this Mandatory Wallet update

Do you have a set of instructions for implementing DigiShield?

@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..

WTF with this shit coin without any innovation

I sent you a pm not sure if it will work but worth a look

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 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.

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 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

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.

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.

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.

Not a good thing to happen. It'd be ok if the hash was spread out but if they're jumping in and soloing on their own wallet or pool, could eventually leave us forked. Thanks for keeping an eye out, I have been up to so much it's hard to really keep watch!

On the top of that I myself have noticed only the pools find the blocks even though the Net hashrate is so much higher than all the Pools combined, Sometimes combined Pool hashrate is also double what the Net hash Reports at times, It doesn't really make sense :/

There has been a solo miner (or pool) jumping on and of with 30MH/s or so and grabbing a few blocks and then backing off until the diff goes down. Occasionally they hit a couple of extra blocks and send the diff way up and stall the chain.

I've been analyzing the block chain (off and on) and network hash rate for a few days now. I've noticed big spikes in the network hash rate  at times with no noticeable difference in the pools combined hash. Someone either has an undocumented pool or they are just soloing and jumping in and out like a multipool to grab some easy blocks.

Something is weird with the retargeting, though... We were at like 5000~% shares for a block just a minute ago, when all other blocks were mining in less than a minute, and instead of a gentle diff adjustment, it was at 2.-something, we finally killed that block and right back down to zilch difficulty. Was beginning to think the chain was stuck and went so far as to fire up a couple of extra nodes to help but nope, the diff retarget is screwy. It shouldn't be making weird jumps like that when hashrate has been fairly steady.

I'll look into it and see if there's anything strange. Oh, and sorry for not checking in the thread more often, been busy with stuff, if anyone needs anything just PM or contact form me!

I tried to post a screenshot, maybe too big.. oh well..
https://www.dropbox.com/s/9mve0ywc6x0wtz3/weird_diff_spike.png

Anyway it doesn't show that it was like 5000% over shares for some odd reason on the block history, but on the dashboard as we were chewing away at it, it did.. I jumped in with my rig to help blast it out of there.

No not stuck, Low Net Hashpower that's why, we just found blocks and are on 32885 now.

stuck on 32878 ?

Blocks are still being found so the Coin is working, the KGW Difficulty Re-targeting might seem weird because of the Low Nethashrate power from what I have been told, although I have asked a Few Other People/Dev's if they could lend a helping hand (BTC Payment) to implement DGW or Digibyte.

Other than that Keep mining Your DRS before the Battalion comes

Might want to look into using DigiShield instead of KGW...