- Devin Burkett, a developer at Grin has released the latest progress on the Mimblewimble Blockchain protocol.
- Mimblewimble is a Blockchain platform that aims at improving scalability, fungibility and privacy of the blockchain networks.
- In the updated mechanism, each mimblewimble header is expected to commit to root of the two Merkle Mountain Ranges (MMRs).
Devin Burkett, a developer at Grin has released the latest progress on the Mimblewimble Blockchain protocol. He emphasized that the primary focus throughout July was on the Initial Block Download.
July Progress Update:
P2P messages added for handling initial state sync. The logic for processing of the downloaded state is partially coded, and will be finished this month. I'm still hopeful for a September Testnet 🤞
— David Burkett (@DavidBurkett38) August 2, 2020
Next Focus Is On The Fungibility Of The Protocol
Mimblewimble is a Blockchain platform that aims at improving scalability, fungibility and privacy of the blockchain networks. Established in 2016, Mimblewimble was launched with the fictitious name of Tom Elvis Jedusor, which apparently is the french for the character Voldemort from Harry Potter. In 4 years of its journey, Mimblewimble has launched two networks to test the mainnet namely, Grin and Beam. Back in 2019, the CEO of Litecoin tweeted about the inclusion of all the major upgrades such as fungibility and scalability in the mainnet. According to him BTC and LTC were only lacking fungibility. Now that they are done with scaling, their next focus is on the fungibility and privacy of the protocol. The development process has continued for over a year and half now.
In BTC/LTC Blockchains, Merkel Tree Is Use To Commit Transactions
According to the developer has emphasized the main focus behind this scalable platform. He said that for verification of the chain, users need to have the knowledge of the outputs. Kernel, which are the small parts of the transaction together with the outputs constituted the ‘chain state’. However, in blockchains like Bitecoin and Litecoin, the merkletree command to commit transactions in the chain. But the mimblewimble developer has implemented a different protocol for transactions because they do not want the users to download all the blocks of Mimblewimble.
The New Initial State Download Protocol (ISD)
In the updated mechanism, each mimblewimble header is expected to commit to root of the two Merkle Mountain Ranges (MMRs). Moreover since the blocks need not to be downloaded anymore, Devin switched the name from Initial Block Download to Initial State Download (ISD). ISD is a reference to the initial sync that he has been working on since the previous month. He further went on dividing the protocol into two peer to peer messages : Firstly, GETMWSTATE which mainly consists of the backbone of a header. Secondly, the MWSTATE which contains everything a user needs to know about the above-mentioned chain state which contains the kernels, unspent outputs and bitmap and parent hashes.
With all the development process being explained, the testnet seems right on track for the September release says Devin.
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?