-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Dd 12 google doc content from Tamara (#14)
* first pass at Tamara's content * prettier formatting * remove duplicate entries * archive unused page * archive page.md * remove dup entry * add ignore for https://github.com/api3dao/dao-docs * fix link with .html, add one link * fix links * prettier * Link validator fails a lot for etherscan * img no longer used * changes from Tamara's comment
- Loading branch information
Showing
43 changed files
with
1,129 additions
and
903 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,7 +23,7 @@ module.exports = [ | |
}, | ||
|
||
{ | ||
text: 'Members', | ||
text: 'DAO Members', | ||
collapsed: false, | ||
items: [ | ||
{ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,93 +1,16 @@ | ||
--- | ||
title: API3 DAO | ||
title: API3 | ||
pageHeader: Overview | ||
outline: deep | ||
--- | ||
|
||
<PageHeader/> | ||
|
||
# API3 DAO | ||
# What is the API3 DAO? | ||
|
||
API3 delegates much of its governance to the vote of a Decentralized Autonomous | ||
Organization (DAO). API3 is a collaborative effort to build, manage and monetize | ||
dAPIs at scale. To achieve delegated governance and apportion grants in a fully | ||
decentralized way, the incentives and processes of the participants are | ||
reconciled through the governance, security, and | ||
[value capture utilities](/overview/pool.md#token-utilities) of the API3 token | ||
and its powers in the API3 DAO. | ||
|
||
The API3 project has a completely open, decentralized and direct governance | ||
model. Any API3 token holder can stake in the DAO pool and obtain direct voting | ||
abilities in the DAO smart contract and thus participate in many aspects of the | ||
governance of the project directly. In addition, stakers receive immutably-coded | ||
[inflationary rewards](/overview/rewards.md) and any additional benefits that | ||
the DAO may decide on in the future. | ||
|
||
The DAO votes on high-level matters such as staking incentives and | ||
collateralization (parameters of the DAO smart contract itself), as well as | ||
grant proposals that directly transfer DAO treasury assets to teams working in | ||
support of API3. | ||
|
||
> <img src="./overview/assets/images/06-a-API3_DAO-Op1.png" width="450"/> | ||
## DAO Contributors Structure | ||
|
||
The organizational structure of contributors which receive grants from the DAO | ||
is often comprised of hierarchical teams and subDAOs both of which manage, | ||
streamline, and secure the success of their deliverables to API3. | ||
|
||
### Hierarchical Teams | ||
|
||
More granular tasks are conducted through hierarchical team structures for | ||
scalable governance. | ||
|
||
A best-practice workflow is to form off-chain teams and apply for grants to | ||
execute one-time projects or time-defined operations that will benefit API3. The | ||
team makes the grant application with a multisig that has the team members | ||
assigned as users, and the DAO permissionlessly transfers the grant to the | ||
multisig if the grant proposal is accepted and passed by the DAO contract logic. | ||
|
||
This team-based governance scheme is scalable in terms of gas costs, as it | ||
requires fewer proposals to be voted on at the DAO level. It is also more | ||
scalable in practical terms, as it does not require the constant attention of | ||
all governing parties to a wide variety of minute details. Furthermore, it | ||
allows critical operations such as dAPI management to be executed swiftly and | ||
based on expert opinion. As API3 operations expand, this governance hierarchy | ||
may demand additional layers in the form of subDAOs. | ||
|
||
To learn more about hierarchical team structures | ||
<a href="/api3-whitepaper-v1.0.3.pdf#page=22" target="_blank"> see Section 5.3 | ||
of the API3 Whitepaper</a>. | ||
|
||
### subDAO | ||
|
||
The DAO is leveraged to selectively allocate funds and decisions in line with | ||
the mission of API3. When a task reaches a scale that can no longer be fulfilled | ||
by a team, it is assigned to a subDAO. | ||
|
||
> <img src="./overview/assets/images/dao-subdao-teams.png" width="350"/> | ||
## Principles | ||
|
||
API3 focuses on two principles for effective governance: | ||
|
||
- Least Privilege | ||
- Transparency | ||
|
||
### Least Privilege | ||
|
||
To limit the amount of damage a malicious or incompetent team may cause, each | ||
team's authority must be constrained to a bare minimum, which is also known as | ||
the “principle of least privilege”. For example, a dAPI management team should | ||
never be able to completely recompose a dAPI that is under use, but should only | ||
be able to switch individual oracles in and out with a long enough cool-down | ||
period to discourage abuse of authority. Similarly, milestones and deliverables | ||
should be utilized to grant teams only the funds needed to carry out their | ||
specific responsibilities. | ||
|
||
### Transparency | ||
|
||
Each team is expected to produce sufficiently detailed progress reports that | ||
enable the DAO's participants to evaluate team performance with respect to | ||
proposed goals. These public reports have the additional benefit of increased | ||
accountability as dAPI users and the general public can audit API3 operations. | ||
data feeds at scale. To achieve delegated governance and distribute grants in a | ||
fully decentralized way, the incentives and processes of the participants are | ||
reconciled through the governance, security, and value capture utilities of the | ||
API3 token and its powers in the API3 DAO. |
Binary file not shown.
Binary file not shown.
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,51 +1,15 @@ | ||
--- | ||
title: DAO Dashboard | ||
title: API3 | ||
pageHeader: Members | ||
outline: deep | ||
--- | ||
|
||
<PageHeader/> | ||
|
||
# DAO Dashboard | ||
# Using the DAO Dashboard | ||
|
||
The [DAO Dashboard](https://dao.api3.org) is the portal to participate in the | ||
API3 DAO. It is aimed at API3 members and others that want to understand how to | ||
interact with the DAO or modify/reuse any of its infrastructure. | ||
|
||
 | ||
|
||
## Preparing to use the Dashboard | ||
|
||
The guides for DAO Members to use the dashboard require a digital wallet such as | ||
[MetaMask](https://metamask.io/download/) to be integrated with your browser. | ||
|
||
1. Access the [DAO Dashboard](https://dao.api3.org) on **Mainnet**. | ||
|
||
2. Install a digital wallet (such as [MetaMask](https://metamask.io/download/)) | ||
for your preferred browser. | ||
|
||
3. Connect your wallet by clicking the **Connect Wallet** button in the upper | ||
right hand corner. Select your wallet from the popup. Be sure your wallet is | ||
connected to the mainnet for production use. | ||
|
||
Once loaded, the dashboard will default to the staking view. On the left is the | ||
annual percentage yield which is the return on investment after one year. Below | ||
that is annual total supply growth. Rewards are updated weekly based on the | ||
percentage of the staking target met, which is calculated by the staked amount | ||
divided by the staking target. | ||
|
||
At the bottom of the page there are two sections, **Balance and Staking**. The | ||
balance section allows you to deposit and withdraw your tokens while the staking | ||
section allows you to stake and unstake your tokens. | ||
|
||
## The DAO Dashboard Guides | ||
|
||
The DAO dashboard has three views as seen in the navigation menu in the upper | ||
left hand corner ( Staking, Governance, and History). Visit the following guides | ||
and learn more about the dashboard functionality. | ||
|
||
- [Staking Tokens](/members/staking.md) - Stake API3 tokens into the DAO pool to | ||
gain governance rights (proposals and voting) and earn rewards. | ||
- [Working with Proposals](/members/proposals.md) - View and create proposals. | ||
- [How to Vote](/members/voting.md) - Vote on proposals directly or through | ||
delegation. | ||
The [DAO Dashboard](https://dao.api3.org/) is the portal to participate in the | ||
API3 DAO. It is aimed at API3 members and others that want to interact with the | ||
DAO or modify/reuse any of its infrastructure. The DAO requires a web3 wallet, | ||
such as [MetaMask](https://metamask.io/download/), to be integrated with your | ||
browser. Be sure your wallet is connected to the Ethereum mainnet. |
Oops, something went wrong.