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

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: ?? on ??

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!

Th3P

sr. member

Activity: 280

Merit: 250

Quote from: DigiByte on February 23, 2014, 02:09:50 AM

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

kimb0

full member

Activity: 154

Merit: 100

Quote from: DigiByte on February 23, 2014, 02:09:50 AM

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

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

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!

hyptonize

newbie

Activity: 14

Merit: 0

Nice professional update guide!!!!!!!

DjstarX

member

Activity: 111

Merit: 10

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 !

mintzone

sr. member

Activity: 285

Merit: 250

Quote from: DakotaW on February 22, 2014, 10:04:39 PM

I just burned out my 6870 mining digibytes Embarrassed

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 Cry

I have faith in digibyte though, and im sure it will eventually be enough to replace my card so i can mine even more! Grin

edit: spelling stuff Roll Eyes

That really sucks. Alot.
Mining with CPU now? Tongue

DakotaW

newbie

Activity: 3

Merit: 0

I just burned out my 6870 mining digibytes Embarrassed

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 Cry

I have faith in digibyte though, and im sure it will eventually be enough to replace my card so i can mine even more! Grin

edit: spelling stuff Roll Eyes

robelneo

legendary

Activity: 3416

Merit: 1225

Still supporting this coin it is indeed has the potential

biboun

newbie

Activity: 56

Merit: 0

Hey, here it is :

cheers

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: biboun on February 22, 2014, 05:10:18 PM

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

Quote

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

Welcome to the community! Whats your DGB address?

biboun

newbie

Activity: 56

Merit: 0

Quote

+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

torchwood-uk

member

Activity: 84

Merit: 10

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.

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: HollowStorm on February 22, 2014, 04:20:58 PM

Quote from: DigiByte on February 22, 2014, 02:25:35 PM

Quote

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

HollowStorm

member

Activity: 70

Merit: 10

Quote from: DigiByte on February 22, 2014, 02:25:35 PM

Quote

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

Gazza1

full member

Activity: 238

Merit: 100

Quote from: zorafex on February 22, 2014, 03:13:38 PM

Quote from: ,./,./ on February 22, 2014, 03:06:16 PM

@digibyte

do you like my video?
can I made what better for you/digibyte/digibytecommination?

or I must be delete the video?

tell me please...

I honestly think it looks really bad. Very nice attempt but with only 11 seconds.. I think less is better. Think "Theatrical" almost like a movie trailer that only shows a "glimpse" of something but makes a huge impact.

Agreed. Not to be negative but that video is very amature. And the audio quality is highly distorted.

zorafex

newbie

Activity: 24

Merit: 0

Quote from: ,./,./ on February 22, 2014, 03:06:16 PM

@digibyte

do you like my video?
can I made what better for you/digibyte/digibytecommination?

or I must be delete the video?

tell me please...

I honestly think it looks really bad. Very nice attempt but with only 11 seconds.. I think less is better. Think "Theatrical" almost like a movie trailer that only shows a "glimpse" of something but makes a huge impact.

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: ,./,./ on February 22, 2014, 03:06:16 PM

@digibyte

do you like my video?
can I made what better for you/digibyte/digibytecommination?

or I must be delete the video?

tell me please...

We are not opposed to any videos people make promoting DigiByte in a positive manner! Looks fine to us!

Thank you for taking the time to put it together!

Any other promotional material you put together is much appreciated. Feel free to use any of the DigiByte logos's etc to do so!

,./,./

sr. member

Activity: 392

Merit: 250

@digibyte

do you like my video?
can I made what better for you/digibyte/digibytecommination?

or I must be delete the video?

tell me please...

DigiByte

legendary

Activity: 1722

Merit: 1051

Official DigiByte Account

Quote from: martins on February 22, 2014, 02:48:41 PM

Quote from: DigiByte on February 22, 2014, 02:39:27 PM

Quote from: The_Cashier on February 22, 2014, 02:22:37 PM

+1 for DigiShield

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

Your development show capacity and humildity to this comunity! a very rare principle with smooth decisions always asking for our opinion... im definitely holding now! had my doubts being honest here! and sorry my bad english, my wife always help me but she's not here.

Thank you for your feedback and support! No worries about the enlgish.

Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1525. (Read 3058921 times)