★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[DigiByte]

// Maximum 400% adjustment...
        bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

[torchwood-uk]

I appreciate you want to get it right the first time but there comes a point when you just need to get something out to stop the multipools, I'm not sure how much lower DGB will go with another week of abuse. A lot of people have already stopped mining DGB, going to be hard to win them back, Digibyte can't grow with only a small community of loyal followers.

[biboun]

+1
Funny, we decided on this name yesterday. It appears all the great minds in the DigiByte community think alike! Glad to see it was arrived at independently of the dev team!

Happy that I proposed that name for my first post ever on bitcointalk

[DigiByte]

+1
Funny, we decided on this name yesterday. It appears all the great minds in the DigiByte community think alike! Glad to see it was arrived at independently of the dev team!

Happy that I proposed that name for my first post ever on bitcointalk

Welcome to the community! Whats your DGB address?

[biboun]

Hey, here it is :


cheers

[robelneo]

Still supporting this coin it is indeed has the potential

[DakotaW]

I just burned out my 6870 mining digibytes   I've been mining every night since the day after launch. Guess i should have watched my temps a little better. Now I need the prices to go up if I want to replace it. No more mining for me   I have faith in digibyte though, and im sure it will eventually be enough to replace my card so i can mine even more!  


edit: spelling stuff 

[mintzone]

I just burned out my 6870 mining digibytes   I've been mining every night since the day after launch. Guess i should have watched my temps a little better. Now I need the prices to go up if I want to replace it. No more mining for me   I have faith in digibyte though, and im sure it will eventually be enough to replace my card so i can mine even more!  


edit: spelling stuff 

That really sucks. Alot.
Mining with CPU now?

[DjstarX]

ok ! So I've been testing my p2pool for the last 24hours, and it's running smoothly , got my miner there , rented some rigs from all 4 corners of the world to try it out and it's a go. Again thank you HollowStorm for the easy guide , guys have a look at it on the reddit page .

http://www.reddit.com/r/Digibyte/comments/1xw61x/p2pool_how_to_make_your_own_personal_p2pool_node/


Can you guys add my node : http://digibyte.no-ip.biz:32412/
located in Montreal Canada . 1%fee


Thx !

[hyptonize]

Nice professional update guide!!!!!!!

[DigiByte]

Great news! We appear to have found the winning combination for the re-target in the DigiShield update!

We discovered the optimum combination was to set a different limit for difficulty increases vs decreases. By doing this we are able to recover or adjust to a 8-10x increase or decrease in net hash within just a few blocks. By having the limits high for both increases and decreases we were able to adjust rapidly to hash swings, but an annoying "oscillation" of block timings emerged. Two fast, then two slow. To fix this we discovered by having lower limits on increases and higher limits on difficulty decreases the oscillation was mitigated and overall performance and re-targeting improved dramatically.

We are now running tests on the network for a few hours to get a running block average and we will also simulate a few more hash swings. We are 99% finished though! Thank you for your support and patience! The extra time we have spent testing over the last 5 days will most definitely pay off for everyone in the long run! With DigiShield we are offering a solution to the re-target problem never seen before in a coin!

[kimb0]

Great news! We appear to have found the winning combination for the re-target in the DigiShield update!

We discovered the optimum combination was to set a different limit for difficulty increases vs decreases. By doing this we are able to recover or adjust to a 8-10x increase or decrease in net hash within just a few blocks. By having the limits high for both increases and decreases we were able to adjust rapidly to hash swings, but an annoying "oscillation" of block timings emerged. Two fast, then two slow. To fix this we discovered by having lower limits on increases and higher limits on difficulty decreases the oscillation was mitigated and overall performance and re-targeting improved dramatically.

We are now running tests on the network for a few hours to get a running block average and we will also simulate a few more hash swings. We are 99% finished though! Thank you for your support and patience! The extra time we have spent testing over the last 5 days will most definitely pay off for everyone in the long run! With DigiShield we are offering a solution to the re-target problem never seen before in a coin!
[/quote

DigiByte to the moon !!!

[Th3P]

Great news! We appear to have found the winning combination for the re-target in the DigiShield update!

We discovered the optimum combination was to set a different limit for difficulty increases vs decreases. By doing this we are able to recover or adjust to a 8-10x increase or decrease in net hash within just a few blocks. By having the limits high for both increases and decreases we were able to adjust rapidly to hash swings, but an annoying "oscillation" of block timings emerged. Two fast, then two slow. To fix this we discovered by having lower limits on increases and higher limits on difficulty decreases the oscillation was mitigated and overall performance and re-targeting improved dramatically.

We are now running tests on the network for a few hours to get a running block average and we will also simulate a few more hash swings. We are 99% finished though! Thank you for your support and patience! The extra time we have spent testing over the last 5 days will most definitely pay off for everyone in the long run! With DigiShield we are offering a solution to the re-target problem never seen before in a coin!

Good to hear

[DigiByte]

Any ETA when the update will drop?

We will drop it around 7 PM UTC time tomorrow (2pm Eastern) as it is late here (2 AM). It has been another long day for us. We are happy with the tests so far. We will mine the testnet over night and get an average over several hours to double check that we are where we want to be.

We are now making sure the wallet syncs with the main net etc. Thanks again for your patience!

[Scyntech]

Any ETA when the update will drop?

We will drop it around 7 PM UTC time tomorrow (2pm Eastern) as it is late here (2 AM). It has been another long day for us. We are happy with the tests so far. We will mine the testnet over night and get an average over several hours to double check that we are where we want to be.

We are now making sure the wallet syncs with the main net etc. Thanks again for your patience!

Looking forward to it guys!

[radi324]

Can someone give me an updated set of nodes for the wallet please?

[ponch85]

the price will drop??

[martins]

Can someone give me an updated set of nodes for the wallet please?

did you read the first page? is there.

[martins]

the price will drop??

i dont know but is already half of actual price because of the multi-pool dumps, but you can always rent a room with me paying with your DigiByte's.

[kimb0]

Why don't we have a android coin ticker?