As Bitcoin Rejects 2MB Blocks, Dash Prepares to Implement Them
Bitcoin, Dash choose different paths toward scalability as Dash prepares to introduce bigger blocks.
In early 2016, the masternodes that comprise Dash’s governance system voted overwhelmingly to upgrade to 2MB blocks, with 99 percent of the network in favor. Many in the cryptocurrency world saw this as a simple attention-getting gimmick, as Dash’s development priorities became focused elsewhere. However, with the recent release of Dash version 12.2, it looks like larger blocks will be implemented soon.
The version 12.2 upgrade is one step on the way to Dash Evolution, the currency’s plan to make “digital [currencies] be so easy to use your Grandma would use them.” Core developer UdjinM6 wrote of the recent update:
The most notable changes are:
- DIP0001 implementation (which is a 2MB block upgrade);
- Transaction fee reduction 10x (activates via DIP0001 activation);
- InstantSend vulnerability fix (activates via DIP0001 lock in);
- PrivateSend improvement which should allow user to have mixed funds available much faster;
- Various RPC changes;
- Lots of backports from Bitcoin Core and refactoring of our own legacy code which should improve performance and make code more reliable and easier to review;
- Experimental HD wallet with BIP39/BIP44 support.
Not needed yet
Of course, larger blocks aren’t needed yet, as the currency does not process enough transactions to fill its current blocks. However, this blocksize increase follows the on-chain scaling plan announced by founder Evan Duffield earlier this year. Duffield announced that through the use of custom hardware, Dash will create a network that can scale to large numbers of transactions by using big blocks.
Many projects in the space believe that on-chain scaling is impossible. That’s simply because they haven’t explored alternative P2P architectures for higher performance. We intend to show just how far an incentivized second tier [masternode] architecture can take a project like Dash.
Bitcoin’s path...and Ethereum’s too
Bitcoin, of course, has chosen to follow a different path. With the planned SegWit2x upgrade officially dead, the currency is now firmly on the path of off-chain scaling through the lightning network or similar solutions. The lightning network is intended to work by moving transactions off-chain onto “payment channels” and then “settling” the result to the Bitcoin Blockchain periodically.
For instance, if Bob pays Alice one BTC, then he later pays her two BTC, and finally sends her 1.5 BTC, that’s three separate transactions that need to be recorded to the Blockchain. With lightning network, however, only the net transaction would need to be posted to the Blockchain once the payment channel was closed. In this case, only one transaction would be posted for a total of 4.5 BTC sent from Bob to Alice.
Critics have asked how often payment channels will really be used, but until the network is deployed, it’s impossible to say. Others suggest that moving transactions off-chain damages the decentralized and immutable nature of Bitcoin. Supporters point out that transactions happen off-chain all the time, for instance on exchanges. No Bitcoin exchange posts a separate transaction to the Blockchain every time funds are moved internally. Only the final result is posted, once a user withdraws funds.
Number two cryptocurrency Ethereum isn’t just sitting on the sidel