mimblewimble team mailing list archive

[Jason <jgtissera@xxxxxxxxx>]

Could I suggest that we release a short roadmap of what the next steps are to get to the final release? I would stay away from timelines unless they are certain.


Have a great day,
Jason



> On Sep 28, 2017, at 4:51 AM, Yeastplume <yeastplume@xxxxxxxxx> wrote:
> 
> For website and messaging, can I suggest, (rather than taking design inspiration from a Hercules graphics card,) just going for a fairly clean, lightly moderated (for technical accuracy) wiki for the time being in the style of https://en.bitcoin.it? This way, we defer major design challenges (perhaps reducing design needs to a logo and basic colour scheme for now). This also might provide a bit more flexibility around documentation, as at the moment all changes and updates to docs have to be PRed, which can get a bit cumbersome.
> 
> YP
> 
>> On 28 Sep 2017, at 00:50, Ignotus Peverell <igno.peverell@xxxxxxxxxxxxxx> wrote:
>> 
>> Hi all,
>> 
>> I've just merged the last large chunk I had on my list before our first testnet, which was the handling of Merklish (MMR) trees to capture our chain state [1]. Before we can setup an actual testnet a lot remains to be done, mostly around testing and reviewing. I do *not* think we should do an actual release (I'm thinking git tag) for this first testnet as it's mostly for developers to play around and start exercising the code. The whole chain WILL BE ABANDONED (at the very least when we migrate from ECDSA to Schnorr sigs).
>> 
>> The different items I'm thinking about are:
>> More testing, both unit tests that may be missing (I need some more for sum trees) and higher level integration. It'd be nice to expand on our simulnet to have a setup with a few miners and few transactors that can be run for some time.
>> A first set of review and audits would be great, especially on core, chain and pool.
>> A pass on the various consensus parameters to make sure they're sane enough.
>> I'll send a separate email about fees later this week.
>> Few items of cleanup like cargo fmt on everything (going to do that shortly) and triaging all the TODOs we have in the code.
>> Some developer doc to explain how to download, compile, setup, run and test. Basic instructions to mine with big words to request the use of only minimal hardware (at least for any longer period of time).
>> A developer focused website (I'm thinking green fixed-width over black) with the proper words or warning and links. Might be a good way to start testing some messaging too.
>> Anything I may have forgotten on the development side? Any additional item that requires more attention at this time?
>> 
>> - Igno
>> 
>> [1] https://github.com/ignopeverell/grin/pull/116/
>> -- 
>> Mailing list: https://launchpad.net/~mimblewimble
>> Post to     : mimblewimble@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~mimblewimble
>> More help   : https://help.launchpad.net/ListHelp
> 
> -- 
> Mailing list: https://launchpad.net/~mimblewimble
> Post to     : mimblewimble@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mimblewimble
> More help   : https://help.launchpad.net/ListHelp