# 7.2. Voting Process

In order for a vote to be called, there are a few requirements:

* **Total Full Cores Required to Call a Vote:** 250 Full Cores must support a proposal to initiate the voting
   process across the network. Each supporting Full Core must burn $50 worth of $DGRAM tokens to
   demonstrate genuine interest in advancing the proposal
* **Total Full Cores Required to Pass a Vote:** A majority is required to pass a vote, balancing practicality
   with community representation.
* **Absolute Majority:** At least 51% of voting Full Cores must vote in favor, with at least 25% of all active Full
   Cores participating in the vote. This equates to a minimum quorum of 2,500 Full Cores (assuming 10,000
   active Full Cores). The number of active Full Cores is calculated based on the 30-day moving average of
   those that have been operational within the network. Quorum requirements can be adjusted over time as
   the network grows, ensuring governance remains practical and responsive.

\
Full Core operators are granted voting rights proportional to their participation in the network. Each Full Core has
 one vote in governance decisions, ensuring a fair and egalitarian system for proposal submissions and decisions.

Governance rules and structures may evolve as the ecosystem grows, as the governance model itself can be
 changed through proposals (e.g. voting thresholds, quorum requirements, burn amounts, and submission limits).

<table><thead><tr><th width="228">Governance Parameter </th><th></th><th data-hidden></th></tr></thead><tbody><tr><td>Proposal Submission</td><td>Open to both Full Core operators and $DGRAM token holders</td><td></td></tr><tr><td>Proposal Burn Requirement</td><td>EcosystemProposers must burn a portion of their tokens to prevent spam</td><td></td></tr><tr><td>Proposal Support</td><td>Must gain backing from <strong>250 Full Cores</strong>, each contributing a small burn amount</td><td></td></tr><tr><td>Voting Quorum</td><td>At least <strong>25% of all active Full Cores</strong> must participate in voting</td><td></td></tr><tr><td>Passing Threshold</td><td>Requires <strong>51% approval</strong> from participating Full Cores</td><td></td></tr><tr><td>Full Core Voting Rights</td><td>Each Full Core has <strong>one vote</strong>, and votes can be delegated</td><td></td></tr><tr><td>Uptime Requirement</td><td>Full Cores must have been <strong>online for 80% of the voting period</strong> to cast a vote</td><td></td></tr><tr><td>Governance Dashboard</td><td>A web-based platform tracking proposals, votes, and results</td><td></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.datagram.network/documentation/whitepaper/7.-datagram-governance/7.2.-voting-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.