The scope of Hard Fork 3 / v4.0.0 was defined last week.
Around January 15, 2021, we expect Hard Fork 4 / v5.0.0 to occur. This is the last of the scheduled hard forks. It’s unclear whether there will be more added, but if things play out according to the current plan, we should not be expecting to introduce consensus breaking changes after that version.
So what really needs to go into v5.0.0 for Grin to be in the best possible shape on the consensus layer by then?
If you have ideas that require consensus changes, v5.0.0 will be your (only?) chance to see them implemented. We’re only a few months away before scope will freeze (around October 2020). Now is as good time as any to make your case.
I’m adding things on the top of my head. Comment below, and I’ll update the list. Some might be targeted for v4.0.0 already, but I think they ought to be listed as well, in case target is missed. The more, the better at this point.
v5.0.0 wish list
in no particular order, or priority, items that are consensus breaking or benefit greatly from being introduced through a hard fork
- Baseline method of transaction building. Some “good enough” approach that can be promoted as the minimally viable transaction building method.
- Relative time locks. To enable future payment channel implementations.
- Soft-fork support. Offering a clear path for conducting soft forks, should we want to.
- Getting rid of txhashset.zip Utilizing RFC#0009-enable-faster-sync to improve IBD process.
- Improvements to dandelion / tx propagation. Not properly defined yet, but perhaps try to iterate based on previous conversations and proposals like Objective-dandelion.
- Support for duplicate outputs. Likely required for simplifying payment channel designs.
What else? Anything that should be removed? Write below!
- April 08: adding duplicate outputs