Difference between revisions of "DigiSpeed"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
Block 1,430,000 Dec. 4th 2015 | Block 1,430,000 Dec. 4th 2015 | ||
− | Activated in December 2015 this was a hard fork that focused on making the [https://bitcointalk.org/index.php?topic=408268.msg13062879#msg13062879 DigiByte coin Transaction speeds faster]. Block time was reduced by 50% to 15 seconds and new block propagation code was added based on [ | + | Activated in December 2015 this was a hard fork that focused on making the [https://bitcointalk.org/index.php?topic=408268.msg13062879#msg13062879 DigiByte coin Transaction speeds faster]. Block time was reduced by 50% to 15 seconds and new block propagation code was added based on [http://www.dgbwiki.com/wikifiles/P2P2013_041-DigiSpeed_Research.pdf Microsoft Research]. This allows DigiByte to handle up to 560 transactions per second. Every 2 years the DigiByte blockchain's dynamic system doubles the number of transactions per second by doubling the block size. In 2017, capability reaches 560 transactions per second, with a maximum capability of 280,000 transactions per second to be reached in 2035. |
Revision as of 02:24, 18 July 2019
Block 1,430,000 Dec. 4th 2015
Activated in December 2015 this was a hard fork that focused on making the DigiByte coin Transaction speeds faster. Block time was reduced by 50% to 15 seconds and new block propagation code was added based on Microsoft Research. This allows DigiByte to handle up to 560 transactions per second. Every 2 years the DigiByte blockchain's dynamic system doubles the number of transactions per second by doubling the block size. In 2017, capability reaches 560 transactions per second, with a maximum capability of 280,000 transactions per second to be reached in 2035.