-
Notifications
You must be signed in to change notification settings - Fork 84
Roadmap changelog
Sebastian Nagel edited this page May 12, 2022
·
3 revisions
This is the changelog of our roadmap. Due to limited space in the included README, we track notable updates here. We usually update it in our (bi-)weekly planning sessions. If you want to join such a session, reach out on Discord!
- Prioritized the Spike about Babbage and serialiseData higher as we started work on it
- In exchange, moved Collect & report metrics and Resubmit network messages to post 0.6.0
- Made Contest logic & OCV 🟢 as we groomed it and understand it well
- Changed Audit coordinated Head protocol 🟡 because scope is still vague, we started work on it though and hope to detail it further or split it into two well-understood issues.
- Similarly, converted Verify implementation against security proofs to an 💭 idea, as it's neither clear whether this is even possible nor required.
- Moved released 0.4.0 features
- Extracted "side-line" topics in the versions view to have "No version". These are not explicitly planned into a release, but are currently being worked.
- Converted Change Client API to a discussion: https://github.com/input-output-hk/hydra-poc/discussions/327 to collect more feedback
- Merged > 0.6.0 and 1.0.0 columns to contain everything needed for 1.0.0, but not scoped into a milestone yet
- Prioritized Contest logic & OCV higher as it is an important missing piece in the protocol and should be present before starting auditing
- Added and implemented connect to chain from point feature, which was a free lunch from rollbacks and something we discovered useful in our hackathon
- Postponed Handle rollbacks II as we achieved a good solution already with Handle rollbacks I
- Postponed Aggregated multi-signatures (using musig2) as we are not limited by it right now and we might be able to simplify musig2 implementation after Vasil HF, see these engineering meeting notes
- Started scoping a 0.6.0 release
- Renamed “re-establish network connections” to Resubmit network messages as this is what we lack in this regards right now
- Added a spike for switching era and evaluating serializeData builtin
- Remove 0.3.0 version column because released (see closed milestones for reference)
- Split 0.4.0 into two releases, where 0.4.0 will already provide access to the public testnet, but only 0.5.0 will be recommended to use (more polish and less footguns)
- Added feature https://github.com/input-output-hk/hydra-poc/issues/240
- From own experience trying to set up distributed load tests, configuring network with knowing all hostnames/IP addresses up front is a pain
- Confirming with users in how they would expect such an API to look like
- Prioritize https://github.com/input-output-hk/hydra-poc/issues/199 higher
- Definitely more important than optimistic head closure
- Maybe even more important. Most use cases seem to require this, so we might even be extending the scope of 1.0.0 if it is unrealistic to attract real-world use without it!?
- Added >> 1.0.0 version column with mostly draft features from now unused miro board
- Added https://github.com/input-output-hk/hydra-poc/issues/214 as some of our potential users are using it
- Added drafts for post 1.0.0 feature ideas
- Added https://github.com/input-output-hk/hydra-poc/issues/203 to focus on current network limitations a bit earlier than planned