Axynom
  • Introduction
    • What is Axynom?
    • Vision & Mission
  • Why Now
  • Founder's Note
  • The Problem
    • Centralized growth traps
  • Token reward inflation and failure
  • Lack of contributor alignment
  • Gatekeeping in Web3
  • Axynom Solution Overview
    • Proof of Growth (PoG)
    • Contributor as a Stakeholder
    • Transparent Rewards and Governance
  • Modular Ecosystem Architecture
  • PoG: Proof of Growth System
    • What is PoG
    • How Contributions Work
    • Voting and Governance Flow
  • GP: Growth Points
  • Role of Admins, Moderators, and Community
  • Examples of Valid Contributions
  • Axynom Token (AXY)
    • Token Utility
    • Tokenomics
  • Transfer Tax Logic
  • Governance Eligibility
  • Vesting and Distribution
  • Staking Mechanics
    • Lock Periods and APY
    • Early Exit Penalties
    • Sustainability Model
  • Treasury and Ecosystem Pools
    • Overview of Pools
    • Role of the Treasury
    • POL Strategy (Protocol-Owned Liquidity)
  • CaaS (Contributions-as-a-Service)
    • What is CaaS
    • Exporting the PoG System
    • Integration Possibilities
    • Revenue Model for Axynom
  • Governance & Voting
    • Governance Phases
    • Voting Power (AXY + GP)
    • Quorum & Approval Logic
    • No ‘Adjust GP’ Rule
  • Gas Economics
    • Why Arbitrum One
    • Axynom L3 Chain with AXY as Gas
  • Product Roadmap
    • Phase 1: MVP Launch (Staking, PoG, Treasury)
    • Phase 2: CaaS, L3 Chain, Scaled Contributor Base
    • Key Milestones
    • TGE Timeline (After Product-Market Fit)
  • Security & Audits
    • Upgradability Practices
    • Modular Contract Architecture
    • Audit Strategy Post-TGE
    • Role of Community Peer Review
  • KPI Forecast & Growth Goals
    • Contributors, GP Points, Stakers, TVL
    • Expected PoG Submissions
    • Treasury Size & Rewards Flow
    • Marketing & KOL Activation Plans
  • Conclusion
    • Axynom Is Not a Product. It’s a Protocol.
    • Call to Builders, Shillers, Designers, Thinkers
    • How to Get Involved
Powered by GitBook
On this page
  • Admins
  • Moderators
  • Community

Role of Admins, Moderators, and Community

The PoG system relies on different participants to maintain order, fairness, and scalability as the Axynom protocol grows. Each role has a defined set of responsibilities that changes depending on the maturity of the ecosystem.

At launch, control is weighted toward trusted actors. Over time, governance is extended toward contributors and community members who have earned influence through participation.


Admins

Admins are the initial stewards of the PoG system. Their responsibilities include:

  • Reviewing contributions for validity and quality

  • Assigning Growth Points for approved submissions

  • Recording contributions on-chain

  • Managing disputes, appeals, or resubmissions

  • Maintaining integrity of GP assignment

  • Finalizing off-chain community voting results (during soft-governance phase)

Admins are expected to operate according to published contribution guidelines. Their actions are visible and subject to review by the broader community over time.

While admins have broad authority early on, their role is intended to become more supervisory as the system matures.


Moderators

Moderators act as an extension of the admin layer. They help scale the review process without centralizing control in a small group.

Moderators are granted the ability to:

  • Pre-screen contributions before admin review

  • Flag submissions that need further clarification

  • Assist in drafting standardized guidelines and evaluation criteria

  • Recommend GP ranges for specific contribution types

Moderators cannot finalize on-chain approvals by themselves in early phases. Their role is advisory and preparatory, ensuring that admins can operate efficiently and that contributors receive faster feedback.

Selection as a moderator is based on a combination of contribution history, reputation (Lifetime GP), and discretionary appointment by the protocol team.


Community

The broader community becomes a critical actor during Phase 2 of the governance evolution.

Community members, if they meet eligibility criteria (such as minimum AXY staked or a threshold of Lifetime GP), are granted the right to participate in contribution voting.

Community participants:

  • Vote to approve or reject pending contributions

  • Influence which submissions receive GP rewards

  • Help enforce contribution standards by majority consensus

Community voting is structured around simplicity. A contribution either passes or fails based on the majority decision. There are no options to edit GP amounts during voting.

Importantly, final recording of approved contributions remains an admin function during the early community voting phase to protect against manipulation and ensure that on-chain data remains consistent.

As the ecosystem grows, further decentralization options, including fully on-chain voting and DAO-managed approval flows, can be introduced through modular upgrades.


The separation of duties between admins, moderators, and the community allows Axynom to balance early-stage efficiency with long-term decentralization. It also ensures that contributors have a pathway to greater influence, moving from participant to moderator to full voting member as they accumulate history and reputation.

Roles are earned, not assigned permanently. Performance, consistency, and transparency govern advancement within the PoG system.

PreviousGP: Growth PointsNextExamples of Valid Contributions

Last updated 1 month ago