Litecoin MimbleWimble Might Recap + Replace


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


Coding & Testing

We’ve made the next vital enhancements to the code over this previous month:

  1. Unified the construct course of to assist present launch methods. We initially meant on sharing the libmw codebase with Grin++, so the brand new code used a distinct know-how (cmake) for managing builds than the prevailing litecoin code.
    That plan turned out to be unworkable as a consequence of vital variations within the Grin and MWEB protocols, so there was now not a motive to proceed utilizing 2 totally different construct administration options.
    We’ve stopped utilizing cmake completely now, and simply embrace the libmw code as a part of the prevailing (automake) construct. We’ve additionally downgraded from C++ 17 to C++ 14 to assist gitian builds, which is how we generate verifiable releases.

  2. Eliminated superfluous interfaces and boilerplate code. This additionally stemmed from the truth that we now not have to share logic with Grin++.
    We had a inflexible interface layer that prevented us from calling the prevailing litecoin code from throughout the new libmw library, which resulted in the necessity to duplicate serialization, logging, and different infrastructure code inside libmw.
    Since litecoin is now the one client of libmw, we have been capable of remove this synthetic separation, leading to much less code (and hopefully fewer bugs) general.

  3. Working automated builds for a number of platforms. The automated builds are working once more for linux, and now additionally a home windows construct is being generated with every code commit.
    This has allowed for faster suggestions from adjustments, and opened the door for non-developers to assist out with testing without having to construct the code themselves.

Critiques & Audits**​**

We’re nonetheless struggling to get builders to evaluation the libmw code. The code has modified fairly a bit because the PR was first submitted although, so I’ll possible be closing it and creating a variety of new, smaller, and hopefully extra digestible PRs over the approaching weeks.

I met with Quarkslab yesterday to debate what we’d like audited, and I’ll proceed to work with them over the following week or two whereas they collect what they should do their preliminary evaluation & estimate for the audit.


We stay on observe for activation across the finish of the 12 months, barring no main surprises from the auditors


Please enter your comment!
Please enter your name here