Informal Roadmap

There are obviously a whole bunch of issues that arose in the past year that were determined to be more important or more urgent than the items on this roadmap. Off the top of my head, that includes the following. (Please note that I’m almost certainly forgetting some items.)

As for the items on this forum post, let me be bold enough to propose the following amendments:

  • Mempool Redesign. Done.
  • Authentication structure authentication. Done-ish. The data that hits the blockchain is the blockchain is compressed (deduplicated authentication structure not list of authentication paths with duplicates); and the code for verifying these in the VM using non-deterministic help exists. However, the authentication structures are presently only verified on the host machine. The last step of this item is to verify these authentication structures on the VM, and require that the block proof certifies this verification in addition to everything else. This last step will be a part of succinctness though. So with one piece missing and it being allocated to a separate bullet point, I think the checkbox is deservedly ticked.
  • Triton VM optimizations. Add to the list: zero-knowledge. Wait, don’t we have zero-knowledge already? The answer is, we don’t know for sure and we certainly don’t have a proof of that fact. We do have a construction for zero-knowledge implemented that comes with a proof but are delaying its deployment because it represents a change to Triton VM that is not backwards compatible.
  • Documentation. Is better. Can be better still though.
  • Competition and bounties. The wallet competition already led to the creation of the VXB wallet. A handful of other bounties have been paid out. The biggest one to have been paid out is the one to OtterSec for finding the vulnerability.
2 Likes