Proposals, Confidential Transactions and what is DigiByte doing?

The proposals can be seen here:

Extension Blocks:

What do these mean? Where are LTC at?

Well, we have the proposals, in and ready for show-time (and feedback)!

Where-to from here for EB / MW for LTC?

From here, there’s going to be several steps:

Why is this so different from how DigiByte did the Odocrypt upgrade?

That’s a great question. I can’t speak as to why Litecoin have gone down this path now for EB / MW, when they didn’t so much with SegWit. I would suggest that SegWit appeared to be a lot more contentious at the time. I can only presume this is because BTC had done all the work with SegWit and the code simply needed an hour or two of merging, whereas this will require significant man-hours to code up almost completely from scratch. Very significant development time.

How does MW differ from Dandelion++ in DigiByte?

When we implemented Dandelion++ in to DigiByte Core 7.17.2, that was not designed to be completely “confidential”, as MW is.

How will DigiByte handle the ProgPOW upgrade?

The code will be implemented in to DigiByte Core, and it will be up to the community to decide if they want to upgrade to a ProgPOW indicating + supporting version, or not. There is absolutely nothing stopping anybody from implementing something, such as Lyra2Rev3 instead.

Will DigiByte be implementing Extension Blocks / MimbleWimble?

At this stage there are no plans to implement either Extension Blocks or MimbleWimble in to DigiByte Core.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Josiah Spackman

Josiah Spackman


I write interesting things about cryptocurrency, especially DigiByte