diff --git a/src/components/modals/AddProposal.tsx b/src/components/modals/AddProposal.tsx index 0ae93e7..def8832 100644 --- a/src/components/modals/AddProposal.tsx +++ b/src/components/modals/AddProposal.tsx @@ -60,10 +60,10 @@ function AddProposal({ isOpen, handleClose, onClick }: AddProposalProps) { onChange={(event: React.ChangeEvent) => handleChange(event) } - placeholder="wxDAI" + placeholder="BRIGHT" />

- How much wxDAI is being governed by Conviction Voting + How much BRIGHT is being governed by Conviction Voting

) => handleChange(event) } - placeholder="wxDAI" + placeholder="BRIGHT" />

- How many TEC tokens are Actively Voting in Conviction Voting? + How many BRIGHT are Actively Voting in Conviction Voting?

- Hatchers will have ~2 million TEC tokens they can vote with. + Hatchers will have ~2 million BRIGHT they can vote with.

) => handleChange(event) } - placeholder="TEC" + placeholder="BRIGHT" /> diff --git a/src/components/tables/ConvictionVoting.tsx b/src/components/tables/ConvictionVoting.tsx index 5ca9015..20a3d59 100644 --- a/src/components/tables/ConvictionVoting.tsx +++ b/src/components/tables/ConvictionVoting.tsx @@ -20,27 +20,27 @@ function ConvictionVotingTable({ diff --git a/src/pages/learn/3.tsx b/src/pages/learn/3.tsx index f82f6dd..c150992 100644 --- a/src/pages/learn/3.tsx +++ b/src/pages/learn/3.tsx @@ -12,36 +12,37 @@ function LearnThree() {

- As your Commons evolves so should its configuration. Parameters within - the different Commons components will be able to be modified after - they have been implemented. In this module you will need to define the - voting requirements for any proposal to alter the Commons + As the BrightDAO evolves so should its configuration. Parameters + within the BrightDAO components will be able to be modified during + deployment. In this module you will need to define the voting + requirements for any proposal to alter the BrightDAO on-chain configuration.


-

Modifying the Commons

+

Modifying BrightDAO


- Tao Voting is the voting process by which the Commons can modify its - economic and governance settings post-upgrade. It is a very powerful - voting application that is capable of performing many high-impact - functions, for example: + Tao Voting is the voting application by which the BRIGHT holders can + modify the economic and governance settings of BrightDAO. It is a very + powerful voting application that is capable of performing many + high-impact Decisions, for example:


    -
  • Mint and burn TEC tokens
  • -
  • Install and remove Applications (Modules) in the Commons
  • -
  • Modify the parameters of all existing Applications (Modules)
  • +
  • Install and remove Aragon Applications
  • +
  • Modify the parameters of all existing Applications
  • +
  • Remove BRIGHT from the Common Pool

- Since there is only one set of voting parameters for all Commons - components, strong thresholds for passing proposals in Tao Voting are - critical to ensure the Commons architecture remains uncompromised. + Since there is only one set of voting parameters for all BrightDAO + components, well thought out thresholds for passing proposals in Tao + Voting are critical to ensure the BrightDAO architecture remains + uncompromised.


- Tao Voting is an upgraded version of Dandelion Voting with familiar + Tao Voting is an upgraded version of DAO Voting app with familiar parameters such as Support Required,{' '} Minimum Quorum, Execution Delay and Vote Duration. @@ -55,9 +56,9 @@ function LearnThree() {

Delegation


- TEC Token holders can delegate their Tao Voting powers to another - member who will cast votes on their behalf, these members become - delegates. Delegates can only vote during the{' '} + BRIGHT holders can delegate their Tao Voting powers to another member + who will cast votes on their behalf, these members become delegates. + Delegates can only vote during the{' '} Delegate Voting Period, which is a specified amount of time at the beginning of the voting process. If a delegate votes contrary to their delegator the delegator can veto the delegated vote @@ -80,9 +81,9 @@ function LearnThree() {

You decide:

    -
  • Legacy Dandelion Voting settings
  • -
  • The amount of time Delegates are allowed to vote
  • -
  • How long to listen for a change of outcome
  • +
  • Normal DAO Voting settings
  • +
  • The amount of time Delegates are allowed to vote
  • +
  • How long to listen for a change of outcome
  • The amount of time that can be added for voting

diff --git a/src/pages/learn/4.tsx b/src/pages/learn/4.tsx index ed3a91a..dc902cc 100644 --- a/src/pages/learn/4.tsx +++ b/src/pages/learn/4.tsx @@ -12,12 +12,12 @@ function LearnFour() {


- Conviction Voting is the governance system in which Commons Members - create proposals to request funds from the Common Pool. + Conviction Voting is the governance system in which BrightDAO Members + create proposals to request funds from the BrightDAO.


- TEC tokens can be staked on these proposals to signal approval of the + BRIGHT can be staked on these proposals to signal approval of the request. Staked tokens accrue voting power, or Conviction, continuously over time. The amount of tokens currently voting on all proposals in Conviction Voting is represented by the term{' '} @@ -27,15 +27,16 @@ function LearnFour() {


- This is the real power behind the TEC token. TEC holders have a direct - impact on funding Token Engineering by reviewing projects and voting - on which initiatives get funded and how much funding they receive. + This is the real power behind the BRIGHT token. BRIGHT holders have a + direct impact on funding BrightDAO ecosystem by reviewing projects and + voting on which initiatives get funded and how much funding they + receive.


The Spending Limit sets the maximum percentage of the Common Pool funds that can be requested by a single proposal. The{' '} - Minimum Conviction dictates how many TEC tokens are + Minimum Conviction dictates how many BRIGHT are needed to pass a proposal, no matter how small the amount requested.