The APIS Docs
HookDiscordContact Us
  • ☺️Hello, Web3!
  • ↔️About The APIS
    • Introduction
    • Core Team
    • Our Partners
  • πŸ€–Roadmap
  • 🍦Products
    • πŸ”Hook
      • Get Started
        • Explore
        • Calendar
        • Collections Trending
        • Watch List
      • Twitter RSS
      • Chatting /w Community
    • ❄️Data Lake
  • πŸ€“Academy
    • On-Chain Glossary
      • NFT
      • DeFi
  • ℹ️$API Token Info
    • πŸ…°οΈ$API Smart Contract Address
    • πŸͺ™Token Economics
      • $API Token Utility
      • $API Token Distribution
      • Dune Analysis
      • Investors
      • FAQs
        • What is API?
        • How do APIs work?
        • What is the API token?
        • Why does API stand out?
        • What does API mean for the crypto industry?
    • πŸ“ˆGet $API Token
    • ⬆️Listed Exchanges
  • 🀝Get In Touch
    • πŸ₯°Contact Us
    • πŸ₯°Join Us
    • ❓FAQ
  • πŸ“–Docs
    • πŸ”Security
      • πŸ“„Security Report by Certik
    • πŸ“„Terms & Conditions
    • πŸ“‘Privacy Policy
    • ℹ️Disclaimer
  • πŸ“ƒWhitepaper
    • Whitepaper
      • 1️⃣1⃣ Background
        • 1.1 Background
        • 1.2 Introduction
      • 2️⃣2⃣ Architecture
        • 2.1 Message Propagation Protocol
        • 2.2 Message Formatting Overview
        • 2.3 APIS Core Contracts
        • 2.4 Governance Contract (GC)
        • 2.5 Dispute Resolution Contract (DRC) Factory
        • 2.6 Optimistic Rollup Contract
      • 3️⃣3⃣ Applications
        • 3.1IDs
        • 3.2 API Token
        • 3.3 Token Distribution, Community Ownership
      • 4️⃣4⃣ Discussion
      • 5️⃣5⃣ Appendix
        • 5.1 REST History and Analysis
        • 5.2 REST APIs in Practice
        • 5.3 Strengths and Weaknesses of REST
        • 5.4 GraphQL History and Analysis
        • 5.5 GraphQL as a β€˜Fetching Tree’
        • 5.6 Anatomy of a GraphQL Request
        • 5.7Note on GraphQL Resolvers:
        • 5.8 Direct Comparison
        • 5.9 Weaknesses of GraphQL
      • 6️⃣6⃣ Bibliography
Powered by GitBook
On this page
Edit on GitHub
  1. Whitepaper
  2. Whitepaper
  3. 2⃣ Architecture

2.4 Governance Contract (GC)

The APIS is upgraded and configured by the decentralized group of API token holders, thus driving the Governance Contract (GC) to be the most important object in the design. The GC is a customized fork from the open-sourced Compound Governance Contract, which has proven to be the most comprehensive, well-audited governance module in the Ethereum ecosystem, as exhibited by its redeployment by other notable layer-two protocols, such as yearn.finance [17]. The purpose of the GC is to allow API token holders to upgrade the APIS Dispute Resolution Factory Contract and the APIS Optimistic Rollup Contract, as well as to implement additional smart contracts into the APIS protocol. API token holders can vote directly or delegate their votes to trusted counterparties; all votes require that the tokens remain locked in the GC for time = 1.504 days (10,000 Ethereum mainnet blocks) after the quorum is reached and the vote is finalized, to disincentivize malicious parties from purchasing API tokens to pass APIS Improvement Proposals (APiiPs) that negatively affect the APIS Network. The quorum required to approve an APiiP will be 25% of the network, although we hope that future APiiPs will vote to raise the quorum requirement as the project becomes increasingly decentralized through the API Liquidity Mining Program, as illustrated further in 3.3 Community Ownership.

Previous2.3 APIS Core ContractsNext2.5 Dispute Resolution Contract (DRC) Factory

Last updated 3 years ago

πŸ“ƒ
2️⃣