feat: add new governance and token sections

components/features/features.tsx

@@ -26,7 +26,7 @@ export function Features() {
   return (
     <div className="mx-auto max-w-full w-[880px] text-center px-4 mb-10">
       <p className="text-lg mb-2 text-gray-600 md:!text-2xl">
-        Your gaming blockchain
+        The Gaming Ecosystem
       </p>
       <div className={styles.features}>
         {FEATURES_LIST.map(({ label }) => (

package.json

@@ -7,7 +7,7 @@
     "url": "git+https://github.com/BuildOnBeam/beam-docs.git"
   },
   "author": "Robby Uitbeijerse <[email protected]>",
-  "license": "GNU",
+  "license": "GPL v.3.0",
   "bugs": {
     "url": "https://github.com/BuildOnBeam/beam-docs/issues"
   },

pages/_meta.ts

@@ -1,6 +1,6 @@
 export default {
   index: {
-    title: 'Introduction',
+    title: 'Overview',
     type: 'page',
     display: 'hidden',
   },
@@ -12,4 +12,12 @@ export default {
     title: 'SDK',
     type: 'page',
   },
+  token: {
+    title: 'BEAM Token',
+    type: 'page',
+  },
+  governance: {
+    title: 'Governance',
+    type: 'page',
+  },
 };

pages/chain/_meta.ts

@@ -3,7 +3,7 @@ export default {
   'get-started': 'Get Started',
   nodes: 'Node',
   builder: 'Build on Beam',
-  'beam-ecosystem': 'Beam Ecosystem',
+  'beam-ecosystem': 'Beam ecosystem',
   resources: 'Resources',
   '--- More': {
     type: 'separator',

pages/chain/beam-ecosystem.mdx

@@ -1,10 +1,10 @@
 ---
-description: "Explore the Beam Ecosystem: Discover official Beam dApps, tools, and resources to enhance your blockchain experience and engagements."
+description: "Explore the Beam ecosystem: Discover official Beam dApps, tools, and resources to enhance your blockchain experience and engagements."
 ---
 
 import { Cards } from 'nextra/components'
 
-# Beam Ecosystem
+# Beam ecosystem
 
 Delve deeper into the Beam ecosystem. Here's an overview of the tools and resources available:
 

pages/chain/builder/network-overview.mdx

@@ -3,7 +3,7 @@ description: 'Dive into the Beam network's comprehensive overview, detailing
 ---
 
 
-# Beam Network Overview
+# Beam network Overview
 
 Here, you can find a comprehensive overview of the Beam network.
 

pages/chain/index.mdx

@@ -33,10 +33,10 @@ import { Cards } from 'nextra/components'
   		</div>
 	</Cards.Card>
 
-	<Cards.Card href="/chain/beam-ecosystem" title="Beam Ecosystem" arrow>
+	<Cards.Card href="/chain/beam-ecosystem" title="Beam ecosystem" arrow>
   		<img src="/beam-icon-ecosystem.png" alt="Build on Beam" />
   		<div style={{padding: '0 16px'}}>
-  			<p>Explore the Beam Ecosystem</p>
+  			<p>Explore the Beam ecosystem</p>
   		</div>
 	</Cards.Card>
 

pages/governance/_meta.ts

@@ -0,0 +1,7 @@
+export default {
+  index: 'Introduction',
+  constitution: 'Constitution',
+  discussions: 'Discussions',
+  proposals: 'Proposals and voting',
+  'dao-entities': 'DAO - Adjacent Entities',
+};

pages/governance/constitution.mdx

@@ -0,0 +1,5 @@
+# BEAM Governance Constitution
+
+The BEAM Governance Constitution establishes a framework for BEAM governance, including an outline of the process for introducing and voting on a Beam Improvement Proposal (BIP). 
+
+Read the BEAM Governance Constitution [here](https://github.com/BuildOnBeam/governance/blob/main/constitution/Beam%20Governance%20Constitution%20(Stamped).pdf).

pages/governance/dao-entities.mdx

@@ -0,0 +1,13 @@
+# DAO-adjacent entities
+
+Currently, Beam Foundation and its subsidiaries, function as so-called ‘DAO-adjacent entities’ in relation to BEAM DAO. The Beam Foundation is a memberless non-profit foundation based in the Cayman Islands, dedicated to the objectives set out in its governing documents, including the decentralization, adoption and security of the Beam ecosystem. It has a mission to make the Beam ecosystem a home for all the gaming needs of users, where users can interact with game related blockchain elements and other applications in a frictionless and user-friendly manner. It being memberless means that there are no ‘owners' of it, making it compatible with crypto values, such as decentralization. As it has no members (shareholders) and is non-profit, it cannot distribute dividends - any assets it owns may be deployed solely towards furthering the growth and development of the Beam ecosystem in accordance with the scope set out in law and its governing documents. 
+
+DAO-adjacent entities, such as the Foundation group entities, enable a DAO to simply be a DAO, while pushing the largest liability vectors (which would be business activities) to limited liability entities that are able to comply with regulations. Beam DAO and tokenholders will not be controllers or managers of the Foundation group (the entities are sovereign), but the [Bylaws, Memorandum of Association and Articles of Association](https://github.com/BuildOnBeam/governance/tree/main/beam-foundation) mandate certain checks and balances on the Foundation group for the purpose of holding the Foundation group accountable, as follows:
+
+- **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.
+
+- **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).
+
+- **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.
+
+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/discussions.mdx

@@ -0,0 +1,17 @@
+# Participate in BEAM Governance discussions
+
+The [Beam Governance Forum](https://gov.onbeam.com) is the place where BEAM governance discussions will mainly be taking place. The Beam Governance Forum serves as a collaborative space for discussions and contributions that drive the development of the Beam ecosystem, including the Beam network, other Beam protocols and the BEAM token. Here, the Beam community is invited to take part in shaping the future of the Beam ecosystem.
+
+The platform consists of a number of categories that encompass a broad range of Beam related topics. Each category has a pinned 'About' post that provides further information about its purpose. The 'Latest' tab will show you the most recent conversations.
+
+If you are new to the Beam Governance Forum, you may join the discussions by doing the following:
+
+- **Create your profile**: Complete your profile setup with an avatar and a concise biography detailing your expertise and interests.
+
+- **Review existing discussions**: Familiarize yourself with the Beam Governance Forum by browsing through threads that interest you. This will give you insight into ongoing discussions and areas of focus within the community.
+
+- **Contribute thoughtfully**: Engage with the community through posts and responses. Note that a user must hold no less than 25,000 BEAM to post a thread in the proposal category, and that any other interaction (such as posting a thread in another category or a comment in any category) requires at least 1 BEAM.
+
+- **Read about the governance process**: To learn more about the governance process, you can read the [Beam Governance Constitution](https://github.com/BuildOnBeam/governance/blob/f6cb77130fae81a268439d7686bf72a194582425/constitution/Beam%20Governance%20Constitution%20(Stamped).pdf).
+
+Read more about participation in governance in the [information & policies](https://gov.onbeam.com/c/information-policies/2)  section of the BEAM Governance Forum.

pages/governance/index.mdx

@@ -0,0 +1,11 @@
+# Governance
+
+In the Beam ecosystem, governance comes in different forms. BEAM is required to participate in BEAM governance. Governance of the Beam network will, after the [Horizon upgrade](/token/horizon), be conducted in a permissionless manner by validators of the Beam network. When referring to governance in the context of blockchains, however, one usually refers to using a token - here BEAM - to vote on decisions about the future of one or more protocols. In that regard, BEAM governance can be divided into two main categories:
+
+1. BEAM governance where a governance decision may result in the upgrades of, or changes to, Beam protocols.
+
+1. BEAM governance where a governance decision is enforceable against Beam DAO-adjacent entities that, through their governing documents, are made compatible with BEAM governance.
+
+BEAM may also be used for voting on matters where the outcome of a governance decision would not be enforceable. While being non-binding, such votes may be used to gauge the sentiment of the Beam community related to different topics and matters.
+
+Even though BEAM governance is an important element of the Beam ecosystem, most activities related to the Beam ecosystem do not require a governance decision. Anyone can contribute to developing the Beam ecosystem or building within it, including to deploy game-related blockchain assets to the Beam network in a permissionless manner.

pages/governance/proposals.mdx

@@ -0,0 +1,40 @@
+# Creation of Governance proposals and voting
+
+A user must hold at least **25,000 BEAM** in order to post a proposal in the proposal category of the Beam Governance Forum. When creating a new proposal, a user is recommended to use the added template as a base for the proposal. See the [Beam Governance Constitution](http://e/blob/main/constitution/Beam%20Governance%20Constitution%20(Stamped).pdf) for further information about the proposal process.
+
+---
+
+#### Submitting a Proposal to a BIP Vote
+
+A proposal may be submitted as an official Beam Improvement Proposal (BIP) vote at [https://vote.onbeam.com](https://vote.onbeam.com/#/), subject to the following criteria:
+
+1.  **Discussion period.** The proposal must, at a minimum, be subject to a 2-day review and discussion period counting from the time it is first published on the Governance Forum. If the content of the proposal is materially changed, then the requirement to have a minimum 2-day review and discussion period shall restart, including for each successive time a material change is made. The author of the proposal may choose a longer discussion period.
+
+2.  **BEAM ownership.** The user submitting the proposal must hold at least 750,000 BEAM.
+
+3.  **Clarity regarding the vote.** It must be clearly stated what the proposal is asking the BEAM tokenholders to vote on, including what is being proposed and what the outcome of a 'for' vote will result in.
+
+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.
+
+
+---
+
+#### Duration of BIP votes
+
+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. 
+
+---
+
+#### Voting rights
+
+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.
+
+---
+
+#### Quorum and majority requirements
+
+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. 
+
+All BIP votes require a simple majority (more than 50%) of the BEAM votes cast to succeed, unless otherwise follows from the relevant smart contract systems. 
+
+Any BIP vote that either fails to (a) meet the quorum requirement or (b) obtain the relevant majority requirement, shall be considered a rejected proposal. However, if a BIP vote does not form a quorum, a repeated BIP vote may take place if the author(s) of the proposal consents and the proposal received more votes 'for' than 'against' during the BIP vote that did not meet the quorum requirements.