Hub
HUMAN Website
  • HUMAN Protocol Document Hub
  • HUMAN Tech Docs
    • Architecture
      • Components
        • Smart Contracts
          • Escrow.sol
          • EscrowFactory.sol
          • Contract Addresses
        • Dashboard
        • Job Launcher
          • Standard
          • HUMAN Job Launcher
        • Exchange Oracle
          • Standard
        • Recording Oracle
          • Standard
        • Reputation Oracle
          • Standard
          • HUMAN Reputation Oracle
        • HUMAN App
        • Annotation Tools
          • CVAT
          • hCaptcha
          • Fortune (test)
      • Protocol Features
        • Routing Protocol
        • Abuse System
        • Qualifications System
        • Governance
    • SDK
    • Tutorials
      • Job Requesters
        • Signup
        • Launch Jobs
          • Fortune
      • Workers
        • Sign Up
        • KYC Verification
        • Wallet address registration
      • Operators
        • Sign Up
      • HMToken
        • Bridge
          • Ethereum <--> Polygon
          • Ethereum <--> Binance Smart Chain
    • Developer
      • Initial setup
      • Running HUMAN Protocol with CVAT
        • Getting started
        • Running CVAT
        • Running HUMAN Protocol
          • Reputation Oracle
          • HUMAN App
          • Job Launcher
          • CVAT oracles
        • Setting up Oracles
        • Setting up Worker user
        • Launch simple CVAT job
      • FAQ
  • Routing Protocol Tokenomics
    • Status
    • Premise
    • Token design
    • Proposition for a governance minimization model
    • Liquidity provision /market making
    • Alternate Conviction voting model
    • Voting model
    • The HUMAN-RP Magistrate
    • Voting process
    • Security
    • Policies
    • Slashing and Soft-freezing
    • Staking for tool vendors
  • Grants Program
    • Introduction and Program Overview
    • Application Process
      • Application Process of the HUMAN Grants Program
    • Funded Projects
    • Community
    • Help & FAQs
    • Terms and condition
  • Guide to the HUMAN Protocol SDK's
Powered by GitBook
LogoLogo

© 2023 HPF. HUMAN Protocol® is a registered trademark

On this page

Was this helpful?

  1. Routing Protocol Tokenomics

Proposition for a governance minimization model

PreviousToken designNextLiquidity provision /market making

Last updated 1 year ago

Was this helpful?

There are multiple options for voting. The following are the most common:

(a) Per-wallet based (1 user, 1 vote)

(b) Share-based (1 token, 1 vote)

(c) – allowing users to “pay” for additional votes

(d) – voting power per token increases per time of lock-up

(e) Alternate conviction – voting power increases each time as well as reputation (i.e. voting power will increase if, for example, you refer valuable projects, solve tasks, or contribute to the overall development)

(f) 1 user, 1 vote, but more tokens locked increases APY in a shared pool

This proposal focuses on option (e), utilizing HUMAN Protocol Reputation Oracles to adjust voting power while providing strong incentives to contribute to the HUMAN project. Apart from the baseline voting power distribution, a question remains about the voting areas within the remit of the token-based governance structure. Given that DAOs can face many challenges, the design needs to clearly define areas that are within scope for voting while protecting against abuse on the network. Currently under consideration are the following areas: dApps, features, enhancements, and HUMAN Protocol versions. As the primary operating entity, Metahuman may initially receive a portion of pool income to supplement the existing HMT treasury. Tying Metahuman to the pool ensures token holders it is aligned with the goal of strengthening the pool, and thus, HMT. One open question is whether Metahuman should be allowed to vote the HMT it holds: to avoid concentration, HUMAN-RP may explicitly block votes from certain wallet sources for a period of time.

Governance minimization model info
Quadratic voting
Conviction