@dfisher I’m not following all of Dom’s tweets and I’m not aware that there is any change in the platform decentralisation decided. I’d recommend to attend the public, global RnD. This is where such decisions would be announced. Also internally.
@lastmjs We already missed quarterly milestones end of the first quarter. I must admit that I didn’t thought about updating the complete roadmap to that and other delays.
TLDR; The delay in the roadmap is mainly caused a higher prioritisation of the BTC and SNS feature and by the decision to finish the storage upgrade on all nodes until end of the year. This also led to the decision to change the way we are setting milestones and thereby untangle dependencies in deliverables. See @samuelburri’s explanation in last public global RnD.
The total delay is mainly impacting the workflow optimisation for NP onboarding and the network growth with these new NP and a Milan-based new node type. There’s still a chance for completing that roadmap by EOY.
I’m referring to this pseudo-gantt from last year November.
Deliverable (A) Reproducible builds: I don’t have the exact time when this was delivered but the corresponding build code is public since January when the corresponding builds passed the acceptance tests. We published a recording of that here.
Deliverable (B) Autonomous Node Deployments: Technically it was done in January with the reproducible builds. The remaining work that was shown for the first quarter was mainly targeting NNS frontend DApp integrations. This was descoped in March because the corresponding team was still working on reworking the complete frontend code to svelt.
We had to rework some details regarding deterministic IPv6 assignments and regarding a VSOCK implementation that allows the replica to do changes on the host system. Due to that delay the rollout “Swap D0 nodes by D1 nodes” started end of Q2 and not end of Q1.
This also delayed the future NP onboarding which is meant to complement the current CLI based onboarding with UI supported workflow. In addition we decided that we would prefer to onboard new Milan-based hardware and not modify the existing Rome-based hardware. I expect the corresponding motion proposal to be placed soon which bring us back on schedule for deliverable (E) Next Node Hardware Generation.
Deliverable (D) NNS-driven data center allocation is still in the design phase. There two things blocking us from starting the implementation: First the NNS team is still focused on the BTC and SNS feature and secondly we found out that the decentralisation code that we currently use to create subnets and replace nodes needs a better testing (more edge cases) before we can integrate it into the NNS. The current node replacements for the storage upgrades help a lot in this regards.