Targets: Testnet v0.4
Resources Required:
- 1 Delivery engineer
- DST
Store Sync protocol was expected to bring reliability to Store nodes, but ended up being disabled as it was found to be resource-heavy. This milestone makes the Store Sync protocol reliable, with performance in line with the other Logos Delivery protocols.
FURPS
Exit criteria
- Expected reliability and performance of Store Sync are agreed with DST at the start of the cycle.
- DST signs off Store Sync against those expectations.
- No known P0 or P1 issues in Store Sync.
Risks
| Risk | (Accept, Own, Mitigation) |
|---|---|
| DST findings late in the cycle | Run the first DST pass in the first half of the cycle, so there is time to fix what it finds. |
Deliverables
Check the Sync protocols specifications state
Owner: Delivery Team
Check with the AnonComms team what the state of the LIP-181 and LIP-182 is, and whether there are changes we would like to make.
Done when: The specification version to implement against is agreed, and the changes we want are raised.
Review implementation of Store Sync protocol
Owner: Delivery Team
Review the implementation against the agreed specification, triage all reported bugs into this milestone, and fix them.
DST sign-off for Store Sync
Owner: Delivery Team + DST
Done when: A DST report covering the agreed expectations is available and signed off.