litecoin need a stimulus release NOW
Nice project update.
But I have not received any Litcoin.
Can anyone help me out on how I can win this reward.
Not entirely sure what you mean. You can purchase Litecoin at most exchanges, along with a good number of Litecoin ATMs. No rewards unless you’re contributing hash power in a mining pool or such.
What rewards do you mean, its an update for mimblewhimble project. It will be implemented to LTC. No rewards in this forum
haha, unlike the US government, we can’t, nor can anyone else randomly print more LTC
Community member Hector Chu worked hard to get the MWEB functionality added to the GUI, and it turned out great! Thanks also to @ecurrencyhodler for helping with the design.
I’ve also started documenting all consensus rules to make it easier for those testing, reviewing, or auditing the code.
I’ll need to take ~1 week to prep Grin++ for Grin’s final planned hardfork. Once I get the new version released, I’ll get builds of the new MWEB code ready and launch the new community-wide testnet so everybody, regardless of technical abilities, can test out the MWEB and provide feedback. Watch for more info about that sometime mid-January.
I still don’t have an exact date ready yet for when the code will be finished, but we’re getting very close. We have a lot of automated tests to backfill still, there’s still a few outstanding questions about max weight for the EBs & peg-in/peg-out maturity, and there’s lots of small cleanup tasks remaining. I’m still expecting to have the code finished sometime this quarter (Q1 2021) though, so it won’t be long.
Happy New Year Everyone!
Haha happy to help.
It’s super cool we were able to keep the Core UI virtually the same for MWEB txns and peg-in/peg-out txns. Hopefully this will make it a lot easier for non-technical people to use MWEB.
Great work so far David!
Also, here’s a very rough prototype on figma of what it’d look like if anyone is interested.
Hi David. This is outstanding.
Have you received enough payment for the work?
Yes, but the fund is getting very low: https://twitter.com/DavidBurkett38/status/1345237931791945728
The UI is very simple, I don’t think it will take so long for a few more people. I hope to speed up, one year is enough to do a lot of things。
Time investment is more terrible than money, money can be earned back, time will disappear forever
Feel free to pass on the need in our little group. We are a purposely small group that passes on information to many social platforms.
How is it going?
Hi David, Hope you are well. Do you have any update for us?
Updates are only in the slow test, you have to donate more Ltc and then tell you
Hello Litecoin community----- I recently reached out to David; I am sure he is quite tied up with all of the development taking place currently. I wanted to genuinely inquire if there were any actions we as a community could take to bolster the testing and successful implementation of Mimble. In addition, if anyone other than David is aware of the current status, please feel free to chime in.
May the force be with us !
I appreciate the enthusiasm from everyone, but please be patient (I’m not even late yet ). If you’ll scroll back and look at my previous updates, you’ll see that nearly every one of them is posted on the evening of the 1st (EST). This month will be no different. I will provide the monthly update in just a few hours. Thanks!
David just told me he has a lot of good news to share.
We were able to get Grin++ ready in time for the hardfork, which went smoothly. That was the final planned fork, so Grin++ is back in maintenance mode, and should no longer be a distraction for the remainder of this project
The bad news - I was not able to get the automated windows build ready, so I did not kick off the community-wide testnet this month like I hoped.
The good news - The delay was mostly a consequence of a new proposal by Tevador (lead developer of RandomX) called MingleJingle. MingleJingle is another design for providing non-interactive txs in Mimblewimble, and by far the most detailed one yet. Tevador was able to use his extensive experience with Monero stealth addresses to make a number of improvements on our design (LIP-0004). The benefits of his design for sub-addresses and output encoding were immediately obvious, so I decided to switch gears for a bit and use what I learned from MingleJingle to improve MWEB addressing and output structure.
The big advantage of this new addressing scheme is that we no longer have to “grind” through different possible stealth addresses when restoring from a wallet seed. With my far-inferior design, the wallet would have to scan the MWEB utxo set and attempt to restore using the private keys once for each stealth address. So if you generated 10 different stealth addresses in the past, it would scan the UTXO set 10 times, which could take several hours after a decade of MWEB usage. While stealth addresses allow reuse without leaking information about your transactions, if you wanted to maintain several identities with a wallet (lame example: multiple pseudonyms on a site like litecointalk.io that each advertise a donation address), then each identity would still need to generate its own stealth address, resulting in these long scan times. But with Monero’s subaddresses (and Tevador’s improved version), we only have to scan each UTXO once, regardless of how many stealth addresses you’ve generated in the past
Some more good news - After finishing the new addressing improvements, I took another pass at the UI and transaction history display and found a number of ways to make it easier to follow where funds are moving. One change I made was to add a new column for MWEB amounts in the transaction history, so peg-ins & peg-outs look a little more intuitive:
The code is now ready for the new testnet, which we can launch as soon as we’ve get a working windows build. If anyone has experience setting up automated builds of bitcoin or litecoin for distribution on windows (preferably using Github Actions, but any CI would be fine), I could really use your help! Come chat with me at Telegram: Contact @MWEB_Testnet
The great news - There are still a ton of ways we can (and will) continue to improve the MWEB code, in particular around syncing, but most of what remains is not required for initial launch. So I think I’m finally ready to commit to a code-complete* timeline…
I will be submitting the code for review on March 15th.
This will contain all of the consensus, P2P, and wallet code necessary for supporting MWEB. The only thing it will be missing is the activation code, which I will add after the reviews and audits are all finished.
* Code-complete means ready for developer reviews & formal audits. It will not be ready for activation until after all reviews & audits are finished.
Happy Groundhog Day everyone! Although COVID killed the in-person celebrations here in Punxsutawney, you can still watch this crucial event unfold live from the comfort of your home: https://www.groundhog.org/
Hi David. Great update. The improvement to add the monero subaddresses by Tevador sounds like a much better way. I look forward to learning more.
Thanks again for all your hard work! I genuinely think you are building a revolution of money & freedom before our eyes.