Bitcoin Forum
May 18, 2024, 02:23:29 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Computing guestimated ROI Change from blocks  (Read 679 times)
gateway (OP)
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
July 30, 2013, 09:36:10 PM
 #1

I'm wanting to work on spitting out some data into a table of current block, block hight, and guestimated diff change.. anyone know of a formula or that could be used to calculate this based upon of course best guess.

Right now I have this data at least getting spit out:

Current Block = 249313
Current Difficulty = 31256960.727769
Current Block Hash = 000000000000006c911cddd6813dd4c680c6b8f3915c853992e1ca15eaa36a3d
Current Block Hash Time = 1375219808 or July 30, 2013, 2:30 pm
Last Block at current Difficulty = 249983
Next Difficulty at Block at = 249984
Next Difficulty in 671
Next Difficulity in 4 days 15 hours 50 minutes

any advice?
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
July 30, 2013, 09:53:32 PM
 #2

The most basic estimate is to look at the amount of blocks mined since the last diff-change and the elapsed time. Divide 10 by the average time per block (in minutes) since the last diff-change and multiply the result with the current difficulty and you obtain an estimate for the next difficulty. Since the network actually computes the new difficulty this way when a change occurs, this estimate gets very accurate close to a change. But early in a cycle, it can swing wildly.
gateway (OP)
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
July 31, 2013, 08:18:24 PM
 #3

The most basic estimate is to look at the amount of blocks mined since the last diff-change and the elapsed time. Divide 10 by the average time per block (in minutes) since the last diff-change and multiply the result with the current difficulty and you obtain an estimate for the next difficulty. Since the network actually computes the new difficulty this way when a change occurs, this estimate gets very accurate close to a change. But early in a cycle, it can swing wildly.

hmm thanks.. lookign into that.. im seeing something weird on a test recent blocks timestamp diff was a negative value how is that so?
kostagr33k
Full Member
***
Offline Offline

Activity: 309
Merit: 100


View Profile
August 04, 2013, 08:56:26 PM
 #4

I actually was looking into this last night and came upon your post.

Will you be releasing this code by any chance?

Kosta
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!