Skip to content

Commit 4be57ee

Browse files
tpellietccamel
authored andcommitted
feat: clarify data space governance mechanisms
1 parent f5559bb commit 4be57ee

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

docs/whitepaper/data-spaces.md

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -88,15 +88,34 @@ Examples of rules
8888
- Retribution of contributors according to the template “Data Marketplace”: each provider evaluates the price of its data or services
8989
- ...
9090

91-
### 2. Governance mechanisms to make these rules evolve
91+
### 2. Governance mechanisms to change rules
9292

93-
Each Data Space decides what are the governance mechanism to change the rules. For instance, it can be a process of proposition and vote by all the members of the Data Space.
93+
Each Data Space can have its own governance mechanism to change the rules.
9494

95-
Governance mechanisms can also be customized to satisfy businesses and small teams (monosigs & multisigs) or decentralized communities (through a custom Data Space token).
95+
#### Centralized Data Space Governance
9696

97-
Note that the decentralized governance of the OKP4 Protocol still allows users to create centralized Data Spaces. Indeed, the governance of a Data Space can be in the hands of one or several chosen or elected members.
97+
When a Data Space is created, the creator can decide to keep the ability to change the rules for himself through a monosig mechanism. It enables him to keep maximum control over the rules. The participants can still make propositions and suggestions, but they can’t vote.
9898

99-
(WIP)
99+
This mechanism can be useful for early communities or for companies who want to keep maximum control.
100+
101+
In this case, the Data Space governance rights holder make sure that participants are still aligned with the Data Space rules and find their own personal interest. The decentralized infrastructure enables participants to stay sovereign over everything they share, they can remove their consents at any moment, within asking the permission from the governance right owner. A period of time can also be defined between a rule change and the effective change, enabling participants to anticipate changes.
102+
103+
#### Permissionned Data Space Governance
104+
105+
In this case, the Data Space governance rights are shared by multiples participants using a multisig mechanism. This brings the possibility for two or more users to change rules as a group in a n-of-n design.
106+
For instance, a 2-of-2 would require the 2 governance rights holders to agree on the same proposal. A 2-of-3 would require 2 of the 3 governance right holders to agree. Mechanisms like a 7-of-10 are also possible in consortiums contexts.
107+
108+
#### Open Data Space Governance
109+
110+
Governance is open when governance rights can be earned or acquired through a publicly traded token. The more stake someone has in the Data Space, the more he has the ability to influence how rules change.
111+
112+
Tokens can also be delegated to trusted leaders if enabled.
113+
114+
**Each Data Space can have its own native token**, which can take a fungible or non-fungible format.
115+
116+
A Data Space can also inherit from an existing token for governance, may it be OKP4 $KNOW token, or another token in the Cosmos ecosystem or beyond.
117+
118+
This brings the ability to have community-governed Data Space with dynamic mechanisms, ideal for decentralized communities.
100119

101120
### 3. Interfaces to create, modify and interact with the Data Space
102121

0 commit comments

Comments
 (0)