Skip to content

Commit 39aadaa

Browse files
chore: format
1 parent e64ea81 commit 39aadaa

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

pages/governance/dao-entities.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ DAO-adjacent entities, such as the Foundation group entities, enable a DAO to si
66

77
- **Onchain**: If applicable, by use of certain programmatic, smart contract-based features, BEAM holders can give onchain feedback to, and provide onchain vetoes against, certain decisions by a Foundation group company.
88

9-
- **Offchain**: By (i) limiting the scope of operation of the Foundation group (i.e., the Foundation group can only operate within the parameters set out in these documents), (ii) having a co-approval right in relation to, and vetoing against, certain decisions by a Foundation group company, or (iii) enabling BEAM holders to seek enforcement actions against a Foundation group company or certain personnel via an 'Emergency Supervisor' in case of an "Adverse Event" (as defined in the documents).
9+
- **Offchain**: By (i) limiting the scope of operation of the Foundation group (i.e., the Foundation group can only operate within the parameters set out in these documents), (ii) having a co-approval right in relation to, and vetoing against, certain decisions by a Foundation group company, or (iii) enabling BEAM holders to seek enforcement actions against a Foundation group company or certain personnel via an 'Emergency Supervisor' in case of an "Adverse Event" (as defined in the documents).
1010

11-
- **Transparency**: By requiring the Beam Foundation to publish and keep publicly available the governing documents, certain reports (including treasury reports) and information as referred to in the documents. The governing documents will remain publicly available (and up-to-date) at all times to enable the Beam community to continue to exert checks and balances on the Foundation group.
11+
- **Transparency**: By requiring the Beam Foundation to publish and keep publicly available the governing documents, certain reports (including treasury reports) and information as referred to in the documents. The governing documents will remain publicly available (and up-to-date) at all times to enable the Beam community to continue to exert checks and balances on the Foundation group.
1212

1313
The structuring of the Beam Foundation and its subsidiaries is inspired by [this article about 'BORGs'](https://delphilabs.medium.com/assimilating-the-borg-a-new-cryptolegal-framework-for-dao-adjacent-entities-569e54a43f83) and [Metalex's work on 'BORG' formation](https://metalex.substack.com/p/the-metalex-whitepaper).

pages/governance/proposals.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,20 @@ A proposal may be submitted as an official Beam Improvement Proposal (BIP) vote
1717
4. **Materially similar proposals.** Any proposal submitted must not be materially similar in content or subject matter to a proposal that was subject to a BIP vote within the past 6 months and that has been rejected. "Materially similar" in this context refers to a proposal that addresses the same issue or matter, contains substantially similar solutions or outcomes, and presents only minor alterations to the previously rejected proposal.
1818

1919

20+
---
21+
2022
#### Duration of BIP votes
2123

2224
A BIP vote shall have a duration of a minimum of 2 days. The author of the proposal may choose a longer voting period when creating the proposal. If during the voting period it becomes impossible to cast a vote because of a wide-ranging non-operability of the voting software or the relevant blockchain system, the vote shall be re-done. 
2325

26+
---
27+
2428
#### Voting rights
2529

2630
Persons that were BEAM tokenholders at the time of the last recorded block number on the relevant voting blockchain system prior to the creation of a BIP vote, and who have held their BEAM on such a voting blockchain system, shall have the right to participate in a BIP vote. Each BEAM on a voting blockchain system carries an equal number of votes, unless otherwise follows from the relevant smart contract systems. Beam DAO-adjacent entities shall have a provision in their governing documents that prohibits them from participating in any BIP vote.
2731

32+
---
33+
2834
#### Quorum and majority requirements
2935

3036
A quorum for a vote on a BIP vote is reached if voting power equaling 1% or more of the circulating supply of BEAM, at the time of the last recorded Beam network block number prior to the end of the most recent quarter (first quarter of a year ending at 24:00 UTC on 31 March) preceding the creation of the relevant vote, has been used to vote on the relevant proposal. 

0 commit comments

Comments
 (0)