Friday, March 25, 2022
HomeLitecoinLitecoin MimbleWimble June Recap Replace

Litecoin MimbleWimble June Recap Replace


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

​——–​

Documentation

I’ve spent a while documenting the entire code adjustments to help our auditors. For these , that is the present checklist of technical paperwork describing the MWEB adjustments (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 stage understanding of the way it works.

LIP-0004 This describes our method to supporting one-sided txs, as a substitute of counting on interactive transactions like conventional Mimblewimble

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

Consensus Guidelines 1 Not a complete checklist, however describes a very powerful consensus guidelines

Kernels Describes how kernels are serialized, the varied options which can be supported (e.g. lock top), and the way new options might be tender forked in afterward.

Information storage Describes the brand new database tables and information information that have been added

Stealth addresses How stealth addresses are generated, how we help subaddresses, how addresses are serialized, and so on.

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

Coding & Testing

I carried out my very own evaluate of the entire node logic to search for methods to enhance safety and efficiency, which resulted in quite a few enhancements to the code & design:

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

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

New stealth handle format that’s extra per earlier handle sorts, together with having higher error detection.

Extra compact serialization codecs for all MWEB information constructions which is able to lead to much less disk area utilization, much less information transferred between friends, and subsequently barely increased throughput.

Higher take a look at protection

Audits and Opinions

I’ve formally handed off the ultimate code adjustments 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 evaluate 5 with essentially the most crucial adjustments to the litecoin consensus code. It’s a lot smaller and extra targeted than the libmw evaluate from just a few months in the past, so hopefully we’ll get extra reviewers and quicker suggestions from different devs.

I’ve made slight adjustments to the estimated timeline on wenmweb.com 23, however total, we’re nonetheless working towards MWEB activation on the finish of the yr.



RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments