LogoLogo
  • Introduction
    • 🚀 Welcome to Datagram
    • What is Datagram?
  • Alpha Testnet
    • What Is Alpha Testnet?
    • Getting Started with the Alpha Testnet
  • Rewards
    • Datagram Rewards System
    • Datagram Points (Alpha Testnet Rewards)
    • DGRAM Token (Mainnet Rewards)
  • Datagram Architecture
    • Datagram Architecture Overview
    • Node Network
    • Fabric Networks
    • Datagram Core Substrate (DCS)
    • The Hyper Network Layer
  • DATAGRAM DESKTOP APPLICATION GUIDE
    • Datagram Desktop Application User Guide
    • Create a Datagram Account
    • Home Screen Guide
  • SETUP DATAGRAM
    • Desktop Application Setup
      • Mac (Silicon, Intel)
      • Windows
    • Partner Substrate Setup
      • Local Machine (Ubuntu/Linux)
      • VPS Servers
  • APIs
    • Get an API Key
  • SDKs
    • Video Conferencing
      • Web (external)
      • iOS (external)
  • Additional Tools
    • CLI (Command Line Interface)
    • Node License Tools
      • Desktop (Full Core License required)
      • Partner Substrate (Partner Core License required)
  • Documentation
    • Whitepaper
      • 1. Introduction & Project Overview
      • 2. Why Blockchain?
      • 3. Datagram Architecture
        • 3.1. The Datagram Node Network & Fabric Networks
        • 3.2. Datagram Core Substrate DCS: The Connectivity Layer
        • 3.3. The Hyper Network Layer
      • 4. Datagram in Action: Real-World Applications & Adoption
        • 4.1. Key Use Cases
        • 4.2. The Datagram Browser
        • 4.3. Business Implementation
      • 5. Tokenomics
        • 5.1. Tri-Token Model
        • 5.2. Supply & Distribution
      • 6. Datagram Rewards & Emissions Model
        • 6.1. Checkpoints
        • 6.2. Emissions Formula
      • 7. Datagram Governance
        • 7.1. Overview
        • 7.2. Voting Process
        • 7.3. Proposal Lifecycle
        • 7.4. Governance Dashboard
      • 8. Datagram Team
      • 9. Conclusion
  • EXTERNAL LINKS
  • Website
  • Dashboard
  • FAQs
  • Blog
  • Discord
  • X
  • Telegram
Powered by GitBook
On this page
  1. Documentation
  2. Whitepaper
  3. 7. Datagram Governance

7.3. Proposal Lifecycle

There are two types of proposals:

  • Funding Proposals: Cover routine decisions such as network policy changes and minor feature additions. Initially, funding is capped at $100k per proposal, subject to change based on network demand and future governance decisions

  • Critical Proposals: Concerns major network changes, such as protocol upgrades or governance structure amendments, and require higher thresholds to pass.

Datagram’s governance system allows both Full Core operators and $DGRAM token holders to submit proposals. However, to maintain proposal quality and prevent spam, a burn mechanism is in place. Before a proposal can advance to a vote, Proposers must commit a portion of their tokens to be burnt, and proposals require support from 250 Full Cores, who must also contribute a small burn to be burnt.

The table below outlines the requirements for both types of Proposer

Proposal Type
Eligibility
Burn Requirement
Support Requirement

Full Core Operators

Any Full Core operator

$5,000 worth of $DGRAM

250 Full Cores must support (each burning $50

Token Holders (Non-Core)

Any $DGRAM token holder

$20,000 worth of $DGRAM

250 Full Cores must support (each burning $50

Once a vote is open, it is live for a set period of time (e.g. 7 days), and each Full Core can cast a vote via a governance platform, with votes shown publicly in real-time. A proposal passes if the required percentage of Full Cores vote in favor, meaning that at least 25% of Full Cores vote (quorum rule) and at least 51% vote in favor of it (majority rule). These thresholds may also be modified in the future, based on governance voting.

A Full Core must have been online for at least 80% of the voting period to cast a vote. This prevents actors from purchasing votes solely to influence outcomes.

Previous7.2. Voting ProcessNext7.4. Governance Dashboard

Last updated 2 days ago