Difference between revisions of "DigiSync"
Jump to navigation
Jump to search
Dgb chilling (talk | contribs) m (Clarifying SegWit adoption) |
Dgb chilling (talk | contribs) (Clarified the name and that DigiSync was a hard-fork, not a soft-fork) |
||
Line 1: | Line 1: | ||
− | In April 2017 DigiByte became the first major cryptocurrency blockchain ([https://medium.com/@josiah_digibyte/clarifying-segwit-adoption-5770b461a860 in the Top 100 of CoinMarketCap]) to implement Segregated Witness ([https://en.wikipedia.org/wiki/SegWit SegWit]) via the DigiSync | + | The DigiSync hard-fork upgrade was named after the major synchronization speed improvements for Core nodes. In April 2017 DigiByte became the first major cryptocurrency blockchain ([https://medium.com/@josiah_digibyte/clarifying-segwit-adoption-5770b461a860 in the Top 100 of CoinMarketCap]) to implement Segregated Witness ([https://en.wikipedia.org/wiki/SegWit SegWit]) via the DigiSync hard-fork. The technical milestone laid the foundation for cross chain transactions and atomic swaps, while also resolving the transaction malleability bug that affected all UTXO blockchains. |
Latest revision as of 04:38, 9 May 2020
The DigiSync hard-fork upgrade was named after the major synchronization speed improvements for Core nodes. In April 2017 DigiByte became the first major cryptocurrency blockchain (in the Top 100 of CoinMarketCap) to implement Segregated Witness (SegWit) via the DigiSync hard-fork. The technical milestone laid the foundation for cross chain transactions and atomic swaps, while also resolving the transaction malleability bug that affected all UTXO blockchains.