Litecoin MimbleWimble June Recap Replace

This replace was written and offered by Litecoin MimbleWimble lead developer David Burkett.



I’ve spent a while documenting all the code modifications to help our auditors. For these , that is the present listing of technical paperwork describing the MWEB modifications (a number of are solely partially full):

LIP-0002 This describes the method for including extension blocks to LTC, together with describing how pegging-in, pegging-out, and integrating transactions work

LIP-0003 3 That is our unique design for Mimblewimble extension blocks. It’s a bit outdated, however ought to present a excessive degree understanding of the way it works.

LIP-0004 This describes our strategy to supporting one-sided txs, as an alternative of counting on interactive transactions like conventional Mimblewimble

LIP-0005 I’m nonetheless filling in lacking knowledge buildings right here, however this paperwork the P2P protocol modifications and describes how MWEB transactions and blocks are serialized

Consensus Guidelines 1 Not a complete listing, however describes crucial consensus guidelines

Kernels Describes how kernels are serialized, the assorted options which can be supported (e.g. lock peak), and the way new options will be comfortable forked in in a while.

Knowledge storage Describes the brand new database tables and knowledge recordsdata that have been added

Stealth addresses How stealth addresses are generated, how we assist subaddresses, how addresses are serialized, and many others.

Pruned Sync 1 Describes how pruned sync will likely be supported in future releases

Coding & Testing

I carried out my very own evaluation of all the node logic to search for methods to enhance safety and efficiency, which resulted in numerous enhancements to the code & design:

Kernel MMR is now per block, as an alternative of a perpetually rising MMR. It was decided that we don’t achieve a lot by having a cumulative kernel MMR, so switching to a per-block MMR means much less time spent hashing, and so much much less disk area wanted to retailer the MMR.

Switched from sha256 to the much-faster blake3 for all MWEB hashes.

New stealth tackle format that’s extra in line with earlier tackle sorts, together with having higher error detection.

Extra compact serialization codecs for all MWEB knowledge buildings which can end in much less disk area utilization, much less knowledge transferred between friends, and subsequently barely larger throughput.

Higher check protection

Audits and Critiques

I’ve formally handed off the ultimate code modifications and documentation to Quarkslab, so we should always have a extra detailed timeline from them any day now.

I’ve created a brand new code evaluation 5 with essentially the most important modifications to the litecoin consensus code. It’s a lot smaller and extra targeted than the libmw evaluation from a number of months in the past, so hopefully we are going to get extra reviewers and sooner suggestions from different devs.

I’ve made slight modifications to the estimated timeline on 23, however general, we’re nonetheless working towards MWEB activation on the finish of the 12 months.

Latest articles

Related articles

Leave a reply

Please enter your comment!
Please enter your name here