3f741f7 · urbit.org · git.iko.soy

git.iko.soy/urbit.org

on master help sign in

voting transaction mechanics

3f741f7drbeefsupreme5 years ago

glossary/upgrade.md−5

@@ -11,8 +11,3 @@ An **upgrade proposal** is a type of [vote](../voting) action taken by the

11proposal, [Galaxies](../galaxy) in the Senate agree to change the

12[Ecliptic](../ecliptic) smart contracts.

14−An upgrade proposal is always a Yes/No vote on whether to adopt a particular set

15−of changes to the Ecliptic contracts. The vote concludes at the end of 30 days,

16−or whenever an absolute majority is reached, whichever comes first. At the end

17−of 30 days the option that has received the most votes is chosen. In either

18−case, the upgrade (or lack thereof) is performed automatically.

glossary/voting.md+10

@@ -11,3 +11,13 @@ members of the [Galactic Senate](../senate), through an [Azimuth](../azimuth)

11smart contract. Galaxies collectively make decisions about the governance of

12Azimuth and the [Arvo](../arvo) network by voting. There are two types of proposals that can be voted on:

13an [upgrade proposal](../upgrade) and a [document proposal](../docvote).

14+

15+A proposal is always a Yes/No vote. The vote concludes at the end of 30 days,

16+or whenever an absolute majority is reached, whichever comes first. At the end

17+of 30 days the option that has received the most votes is chosen.

18+

19+In the case of absolute majority, the vote transaction that achieves that

20+majority triggers the upgrade or document ratification. In case time runs out,

21+an explicit "update vote status/check result" transaction will need to be made.

22+This can be performed by anyone at any time. Any effects from doing so will only

23+happen if there was a majority vote in favor.