What is happening?

On December 27th, 2017 the Proof of Capacity Consortium released a white paper detailing a plan to upgrade the Burst network entitled "The Burst Dymaxion". This will introduce many new feature as well as improvements to current features. To accomplish these changes a number of Capability Improvement Proposals (CIPs) and forks will need to take place during 2018. It is imperative that you understand what a fork is and the impact of a fork in the context of cryptocurrency (A simple article explaining forks is at the bottom of this page).

List of major changes the Dymaxion will bring

  • Dymaxion Layers (off-chain tangle networks)
  • Dynamic Block Sizes
  • Dynamic Transaction Fees
  • Proof of Capacity 2.0 (elimination of time-memory trade off vulnerability)
  • Proof of Capacity 3.0 (plot that will store data important to humanity)
  • Ring Signature Anonymity
  • zkSNARK Anonymity
  • Improved Atomic Cross Chain Swap Support
  • Improved Smart Contract Support

For a more technical explanation of the features listed above, please refer to the white paper listed below.  

What must miners do?

You must be using the most current version of the PoCC wallet (currently 1.3.6cg). All wallets of version number 1.3.6cg or lower are able to communicate with any other wallet, of any version number. When BRS 2.0.0, the building block wallet for future Dymaxion implementation is released, it will only be able to communicate with wallets 1.3.Xcg or newer. As people continually upgrade from 1.3.6cg to BRS 2.0.0 it will become more likely that your wallet will no longer be able to correctly synchronize the blockchain and will eventually fork.

In 2018, there will be multiple new wallets as more features are added to the codebase. Upgrading a wallet is not complicated and should not be viewed as "difficult" or "a big deal". If you need support, the Burstcoin subreddit, telegram, and discord are all filled with helpful people. Since consensus is determined by the percent of public wallets (guide to setting up a full node) using the newest version, this metric will be unsurpassed in importance in determining how fast the next step can proceed. The faster the community upgrades, the faster the timeline can progress.

On Windows, Qbundle is a very nice wrapper that will take care of almost the entire install process for you, and most importantly, give you the ability to upgrade to new versions of the BRS wallet, Qbundle, Java, and database software with a simple, one-click option. EcoMine has a tutorial to walk you through setting up Qbundle.

On macOS, you can follow either follow the tutorial provided by EcoMine to set up the wallet manually, or use Andrew Scott's script that will automaticall take care of the installation for you. It is important to note that on macOS there is no one-click upgrade option, so you must stay aware of new releases to keep all your software up to date.

On Linux, CryptoGuru hosts a package repository to aid those working on Debian or Ubuntu.

Once PoC2 is implemented, replotting will NOT be a requirement, however a read speed reduction of 50% will occur until the plots are optimized and transformed into a PoC2 plot. Both plotters and optimizer will be released to directly generate new plots and optimize current plots respectively. The optimization software will not be CPU or GPU intensive, but I/O intensive.

Once PoC3 is implemented, replotting will still NOT be a requirement, nor will a read speed penalty be incurred. Mining with PoC3 capable plots will be at the discretion of the miner since PoC3 will co-exist with PoC2.

PoC3 is officially considered post-Dymaxion, but because it was introduced in the white paper it is still listed here.

Assuming that a miner has successfully remained on the main chain, whether through pools or by managing their own wallet, and disregarding the optional plot optimization for PoC2, there will be no direct impact on how mining is conducted compared to today. The first assumption is critical though, because if a miner, either purposefully or accidentally (most likely thorough using a pool that did not upgrade correctly or did not support the Dymaxion hard forks initially), ends up mining on a fork, all of the time, effort, and potentially BURST (however this new form of Burst will not be considered 'Burst' as it is now) will be lost in terms of the main chain. 

If a miner does end up mining on a fork, it is not a catastrophe. The plots will remain valid for mining on the main chain, and all that is required is for the miner or pool to resync with the rest of the network on the main chain, but this will result in effectively "restoring" your address to the state it was in during the block prior to the block where the two chains diverged (eg. balance will be reset and all transaction newer than the block where the fork occurred will be negated as they did not occur on the main chain).

When pool mining, a local wallet is technically unnecessary for the purpose of mining. The wallet that the pool is using (aka the rewards recipient) is the only wallet relevant to submitting deadlines. Thus, the advantage to mining on a pool supporting the Dymaxion hard forks will be that any individual miner on that pool does not need to worry about running and upgrading the correct wallet or staying on the main chain, but you must remain aware, at the time of the fork, to verify that the pool operator has successfully followed the correct chain.

Please refer to EcoMine's list of pools confirmed to be supporting the Dymaxion hard forks to find, join, or switch to a pool.

When must miners make changes?

There is no dated timeline (in calendar or block time) to indicate the fork schedule although as we approach each successive fork a specific block height (and approximate date) will be announced. The PoCC believes that completing all three fork is possible within the first half of 2018, but community adoption of the new wallets will be the gauge of just how fast these forks can progress. Its is explicitly NOT the intention of the PoCC to implement any contentious hard forks, meaning that all upgrades will come after consensus (greater than 80% of the network) is reached in the form of running up to date wallets. This consensus also includes the exchanges upgrading to the new software.

  • First hard fork: includes dynamic block size and transaction fees, the PoC2 protocol and some of the Dymaxion code, but inactive. The fork is planned to happen around block 470 000 – probably not before March.
  • Second hard fork: implementation and activation of the remaining Dymaxion code. Users should be able to play with it on the TestNet before that.
  • Third hard fork: Implementation of the PoC3 protocol.

When a concrete block height for a fork is announced, it will also be listed on this page to make the absolute deadlines extremely clear.

If you found this especially helpful, donations to keep the website up are always appreciated.