Dear WINGS community,
During Q1, among other things, the team has been extremely busy restructuring and laying the foundations for increased development performance. In result, while we are working in parallel on the new blockchain direction, we were able to release FEATHER, the WINGS design toolkit, and open-source our lightweight wrapper library.
Since its inception, WINGS DAO was designed to become a decentralised protocol, owned and managed by a distributed, autonomous organisation of collaborating developers and community members. And while the end goal was always clear, the road to it was often long and tangled. Today we would like to present a preview of one of the mechanics we have been working on, a milestone that will finally take us closer to that end goal — the WINGS Protocol upgrade system, which will enable the community to propose, vote for and fund new features and functionalities for the WINGS ecosystem.
The upgrade system is a tool that allows community members to propose and develop changes to the WINGS Protocol. Anyone that has an idea that they believe would make the WINGS Protocol better, more secure, or increase the WINGS adoption, will be able to create an upgrade proposal. The upgrade process is designed to be as simple as possible, and requires only a few steps:
1. A new upgrade proposal is created
2. The proposal is reviewed and is voted on by the community for approval/rejection, initially defined by a majority of voters. A minimum number of tokens participating in the vote will be required before a resolution can be reached, currently being 20% of total WINGS tokens supply). (Both the approval percentage requirement and the minimum number of voting tokens required, are subject to change prior to release.)
3. The community funds the proposal (if the proposal requires funding)
4. If approved and funded, the development process begins
5. The new code is submitted for review
6. If approved, the new code is integrated into the Protocol by a Warden (see below):
A Warden is an elected entity such as a trusted community member, that is allowed to merge code into the mainnet branch. A Warden’s task is to (i) verify that the submitted code matches the approved proposal description and (ii) to ensure that the proposal is logical and was approved by the community properly. A Warden may reject an already approved proposal and request a higher majority and/or higher vote participation rate if the proposal introduces significant, risky or illogical changes. The initial Warden will be the Wings Foundation, with a mechanism to elect additional Wardens or replace existing ones to be introduced in the future.
Below you can find a few screenshots from the upcoming system; please note, that this is a preview only, and the final functionality might differ.
It’s also important to note that the above mechanics will have a special role in the upcoming new WINGS blockchain. We will be posting more information as the new blockchain’s features are finalised.
More to come, please stay with us while we make WINGS great again, together!