April 30, 2025, 08:33:01 AM

Author Topic: [Official] Daily(almost) Update Thread  (Read 67965 times)

0 Members and 1 Guest are viewing this topic.

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #30 on: June 17, 2015, 08:59:20 PM »
Today's Updates(check post date):

  • Sorry guys I'm still under the weather.. Will update you tommorow
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #31 on: June 18, 2015, 07:24:41 PM »
Today's Updates(check post date):
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #32 on: June 19, 2015, 02:53:25 PM »
Today's Updates(check post date):
  • Continuing Test case evaluation code..
  • Continuing on Sunday.. Logging off 8:18 PM
« Last Edit: June 19, 2015, 08:18:48 PM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #33 on: June 22, 2015, 09:55:14 AM »
Today's Updates(check post date):
  • Finishing up test case code.
  • Generated randoms have lower bound bias. Fixing..
  • Fixed issue. Was a problem with random value being rounded up which was causing the most probable scenario, id=0 for the probability set not being chosen.
  • Finding optimal adjustment values..

As you can see below the goal is a curve that can drop quickly but rises slowly.. (see the behavior of the blue line). The gold line is ideal and green is what we currently have. Our current difficulty algorithm is actually on the spot but this is only for case like this where hashpower rises steadily. I'll do some tests with some fringe cases (like the one our network is currently experiencing).



  • Signing off.. 8:18PM doing fringe test cases tomorrow/also need to check for timing attack parameters
« Last Edit: June 22, 2015, 08:20:00 PM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #34 on: June 23, 2015, 12:17:27 PM »
Today's Updates(check post date):

Today I finish up the algorithmn.

  • I noticed some value locking.. investigating prior to doing fringe test cases.
  • Found and fixed value locking issue.
  • Doing fringe test cases
  • Finished 3/4 fringe test cases.. It's getting late and there seems to be some issue simulating our current situation.. continuing later..
  • Signing off 3:28AM
« Last Edit: June 24, 2015, 03:28:17 AM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #35 on: June 24, 2015, 06:18:20 PM »
Today's Updates(check post date):
  • Finishing up last fringe test case..
  • Something strange is going on with my editor.. the test cases are done.. but for some strange reason I'm getting strange result sets. Bugs that don't make any sense and then when I trace them and find them to be virtually impossible.. and I run the client again.. suddenly the set changes to something that makes even less sense.(Like I've broken the potential result set in reality or something) I tried restarting my editor too.. Maybe some memory corruption? I dunno, everything else is running fine and I tested this system to be prime95 stable overnight.. In any case will continue tomorrow
  • Signing off 2:55AM
« Last Edit: June 25, 2015, 02:58:04 AM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #36 on: June 25, 2015, 01:11:13 PM »
Today's Updates(check post date):
  • Continuing tweaking of fringe cases.
  • Some unforeseen bugs need fixing.. continue later..
  • Signing off 12:54 AM
« Last Edit: June 26, 2015, 12:54:45 AM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #37 on: June 26, 2015, 06:08:17 PM »
Today's Updates(check post date):
  • Taking a break.. Will be back Sunday.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #38 on: June 28, 2015, 07:26:24 PM »
Today's Updates(check post date):
  • Entertaining guests.. sorry for the delay.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #39 on: June 30, 2015, 06:36:43 PM »
Today's Updates(check post date):

  • Taking a little break.
  • No worries I'll be back tomorrow.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #40 on: July 01, 2015, 10:15:15 PM »
Today's Updates(check post date):
  • Something arrived that demanded my attention for most the day (9+ hours of work :|)
  • Fret not over the difficulty change,the algorithm is done and needs a few more adjustments before release.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #41 on: July 02, 2015, 02:24:51 PM »
Today's Updates(check post date):
  • Finished algorithm.. Planning to implement tomorrow/Sunday.
  • Test case results below:

In these tests you will see a golden line which shows the difficulty under IDEAL situations (little to no randomization) under the CURRENT difficulty algorithm. It does not represent where the difficulty should be at any given hash-power(so don't be confused into thinking it means that).

These tests are performed with an initial difficulty and hash rate(to better model the switch) which is why you may see a little discrepancy at the beginning of the charts. The old difficulty algorithm performed a difficulty change every 60 blocks.. the new one performs a difficulty change on block. Further investigation on possible consensus issues with this will be investigated(if I have time to spare).

The blue line is the NEW algorithm with probable block times and the green line is the CURRENT difficulty algorithm with probable block times.

(IE: try to compare Blue vs Green)
 
First on the list is our current predicament.
Here you can see the new algorithm resists the attack's attempt to increase the difficulty artificially whereas the old algorithm ramps the difficulty up.


Next you may see the case where we have a fast linear drop. Here you can see that the difficulty does stutter a bit under the new algorithmn but remains BELOW what it would be with the current algorithm and then stabilizes with the hashpower.


Next you may see how the difficulty stabilizes well under a constant hashrate


Now you may see how the difficulty stays at the ideal level or below with a steady gain of hashrate.

The downward spikes are a very interesting property. These groups of <100 blocks of low difficulty can help ease network congestion and remove the current block size issue bitcoin is facing.


Now you may see that with sinusoidal gain, even with vast difficulty changes, it manages to match the hash power curve as the old difficulty algorithm did.


Now you may see that a slow linear drop handles much in the same way as a fast one. No strange deviations noted here imo.


Now you may see that in a step gain scenario, the new difficulty algorithm matches or beats the old one(on average) at any given hashpower for block solving time probability target time of 2 minutes.


  • 1:43 AM - Signing Off.
« Last Edit: July 03, 2015, 01:51:46 AM by akumaburn »
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #42 on: July 03, 2015, 06:53:07 PM »
Today's Updates(check post date):

  • Taking a breather, be back on Sunday.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #43 on: July 05, 2015, 08:14:56 PM »
Today's Updates(check post date):

  • Doing some curve adjustments that are taking unusually long.
  • I'll update you tomorrow.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd

Offline akumaburn

  • Lead Developer
  • DevTeam
  • *****
  • Posts: 320
  • Karma: +44/-0
    • View Profile
Re: [Official] Daily(almost) Update Thread
« Reply #44 on: July 06, 2015, 05:06:47 AM »
Today's Updates(check post date):
  • No updates today.. didn't get any sleep.
Want to donate to the Development Team?

GLD:
DztaVPtUd2M5TwfifBUaq5bLrAscYeMbyd