They sure did and it should.
I don’t know the process 100% but the gist is anyone with a “roll” (10,000 tezzies) can vote. People who do not have a whole role can delegate to a baker and that baker can accumulate voting power. As long as a super majority of bakers vote in favor of an injected proposal it will take effect.
Also as you say, we don’t have bakers or delegates rather we have elders and sections.
The most important part really I think is the ability for an update to be injected and adopted with no forking, and they seem to run some kind of parallel nodes to test the upgrades, plus a ton of thought goes into an upgrade and there is a ton of active participation amongst bakers and developers, which makes me curious with a decentralized and anonymous web how we can address that openness and remain resilient.
@dirvine has mentioned in the past that there could be sacrificial nodes with the updated version that run alongside others to check for expected behavior and perhaps the Elders within a section vote for this to happen. In Tezos, the bakers want to keep their delegates because they take a cut of the baking rewards and as a baker if you don’t vote on a popular proposal then those delegates will not be happy and move to another baker. We may need some similar form of incentive to keep Elders accountable to important upgrades, perhaps punishment?
If I understand correctly we have an important component of upgrades being built right now, yes? Idempotent sections using Anti-Entropy, like CRDT for sections. So that way sections have a way of propagating the update and all come to an agreement in a lazy way.
It’s the injection, vote or adapt upgrade, and Elder accountability to section participants parts that will probably be the trickiest bits I’m guessing.
On the topic of launch, I think the tweaking of token economics is being ignored a bit in this discussion and will take some time to tweak to get right. The fact that the new member is FinTech and will help focus on tokenomics means Maidsafe is gearing up and should be ready for it
We aren’t yet sure how much SN Token might be valued at, how we will try to increase demand for SN Token, how much app developers will earn from PtD (I’d love to know! lol) also how PtD will be enforced or if any published item like a blog could be applicable, which I advocate for.
I would like for users within an app to not only control their own data but also curate public data and be rewarded for its popular consumption, by self publishing that curated list of others (already published and earning PtD) content. PtD could do this just as well as PtP, in my opinion. Having to add an app specific token for this or fulfilling several different roles gets overly complicated and muddy.
This last bit about PtD reward amounts and accessibility is something that should take some deep consideration and I haven’t seen it get discussed so I imagine that will add to the timescale a bit but would love to start discussions about that now if anyone else is interested.