From Vision to Reality: SSV DAO’s Historic Step Toward Making DVT a Community-Owned Public Good
Transferring smart contract ownership to the SSV DAO. Yet another step to a fully decentralized and community owned ssv.network.
Like many other industry-leading public goods in the blockchain space, governance is decentralized through the community and elected representatives. The ssv.network has long strived to embody this ethos, step by step, democratizing access to secure, efficient, and reusable DVT infrastructure.
At a high level, this blog post will look at the steps the SSV DAO has taken toward this goal, how [DIP-2] Multi-Sig Committee is a major milestone in this mission, why it’s important, and where the SSV DAO goes from here. Don’t forget to join Mainnet Call #3 for everything you need to know about the second last stage in the mainnet rollout, the Launch phase.
TL;DR
Since day 1, the ssv.network was developed with a vision and purpose in mind. It all boils down to becoming the layer that helps secure and decentralize Ethereum’s PoS consensus & distribute that power into the hands of the community. Now that the mainnet launch is well in motion, it is truly exciting to see this vision become a reality.
The approval of the DIP-11 Mainnet Proposal marks another historic day — full control over the network’s smart contracts has been transferred to the SSV DAO Multi-Sig address.
The ssv.network DAO was established two years ago. Since its inception, the DAO has managed to self-organize and lead strategic projects on behalf of the community, such as the DAO partner program, contributor on-boarding, and various vital committees.
This was essential in becoming a community-owned public good in the ETH staking space. After years of public testnets and ecosystem building, the protocol has arrived at the mainnet rollout — a significant milestone to a fully permissionless DVT protocol.
During this vital phase, the SSV DAO reformed the grants program and grants committee, allowing them to choose the Mainnet Verified Operators and Mainnet Launch Partners (which will be whitelisted by the multi-sig on the 14th of September) for the ssv.network Mainnet Launch by a simple majority vote.
Another vital committee that was established was the Multi-sig Committee. It acts as the safe keeper of the DAO’s treasury and provides a layer of security when executing votes made by the community. The SSV DAO recently passed a vote to put more governance power into the hands of the SSV DAO multi-sig and give it control over the ssv.network smart contracts instead of having a single point of failure. This transition is tangible proof of the ssv.network evolving into a community-driven enterprise. For a closer look, you can see the transactions here and here.
By looking at the proposals in Snapshot from last year, one can see the protocol is slowly being handed over to the SSV DAO. One of the final steps in this mission is achieving the Permissionless launch, which follows the Launch phase (pending DAO approval). A few more optimizations and the mission is essentially accomplished — the ssv.network as a public good, DAO-driven, community-owned, DVT pioneer.
Now that the [DIP-2] proposal has passed, the Multi-sig Committee responsibilities, compensation, members, and work procedures have been solidified and will replace the previously approved Multi-Sig Committee Formation. This decision has various positive implications for the decentralization and security of ssv.network smart contracts, treasury, and all-around decision-making.
Ssv.network as a whole embodies the ethos it was built with. Full decentralization, mitigating single points of failure, and is fully permissionless, community-owned, and open-sourced.
The SSV DAO believes these values will allow the ssv.network protocol to become the leader in DVT. By being permissionless and simple to use, builders can create diverse on-ramps to DVT-based staking applications for every staking use case. Jato-v2 testnet is now live and open to the public. Start testing and get a taste before the mainnet goes permissionless later in Q4!
Website | Network Hub | Discord | Dev Center | Documentation | GitHub