HbarSuite Docs
  • Welcome to HbarSuite
  • HbarSuite Developer Documentation
    • HbarSuite Smart Engine Applications
      • @hsuite/cross-chain-exchange
      • @hsuite/dao
        • DAO Application Testing
      • @hsuite/exchange
      • @hsuite/launchpad
      • @hsuite/multisig
      • @hsuite/nft-exchange
      • HSuite Smart App - Enterprise Hedera Application Framework
    • HSuite Libraries
      • @hsuite/api-key - Enterprise API Key Authentication System
      • @hsuite/auth-types
      • @hsuite/auth - Authentication Module
      • @hsuite/client-types
      • @hsuite/client - Client Service Module
      • @hsuite/dkg-types - Distributed Key Generation Type Definitions
      • @hsuite/hashgraph-types - Hedera Hashgraph Type Definitions
      • @hsuite/health - Comprehensive System Health Monitoring
      • @hsuite/helpers - Utility Library
      • @hsuite/ipfs - InterPlanetary File System Integration
      • @hsuite/shared-types - Shared Type Definitions
      • @hsuite/smart-config - Configuration Management
      • @hsuite/smart-ledgers - Multi-Ledger Management
      • @hsuite/smart-network-types - Smart Network Type Definitions
      • @hsuite/smart-transaction-types - Smart Transaction Type Definitions
      • @hsuite/smartnode-sdk - SmartNode Software Development Kit
      • @hsuite/snapshots - Multi-Ledger Token Snapshot Management
      • @hsuite/subscriptions-types - Subscription Management Type Definitions
      • @hsuite/subscriptions - Enterprise Subscription Management System
      • @hsuite/throttler-types - Rate Limiting Type Definitions
      • @hsuite/throttler - Advanced Rate Limiting for NestJS
      • @hsuite/users-types - User Type Definitions
      • @hsuite/users - User Management Module
      • @hsuite/validators-types
  • General Documentation
    • Smart Apps and Interaction
      • Subscription-Based Model
      • Token-Gate Model
    • The Smart Node Network
      • security-layer
      • Type of Validators Explained
      • Understanding Validators in Our System
      • Automating Responses to Network Changes & Key Rotation
      • Ensuring Continuous Operation and Recovery
      • Generating and Sharing Keys Collaboratively
      • Handling Node Expulsion and Replacement
      • Managing Cluster Membership
      • Protecting Secrets with Shamir's Method
      • Security Layer Integration
      • Setting Up Secure Clusters
    • Tokenomics
      • Tokenomics v1
      • Tokenomics V2
    • What is a Smart Node?
  • Restful APIs Documentation
Powered by GitBook
On this page
  • Automated Security & Treasury Management
  • Core Team Operations Allocation & Funding
  • Dynamic Treasury Allocation
  • Smart Node Runner Rewards
  • Staking Returns
  • NFT Subscription Model
  • Developer Access System
  • Deflationary Mechanism
  • Token Burning Process
  • Ecosystem Growth
  • Smart-App Marketplace
  1. General Documentation
  2. Tokenomics

Tokenomics V2

Automated Security & Treasury Management

  • All token-related operations (freeze, wipe, mint, etc.) are secured through an automated multi-signature system of multi-signatures.

  • The HSUITE Treasury implements automated multi-signature of multi-signature controls (Manual Operations thorugh the council members will be deprecated).

  • Treasury HSUITE tokens are managed through automated DAO proposals, maintaining flexibility for fund management and project growth.

Core Team Operations Allocation & Funding

  • While the community core team is not requesting a fixed HSUITE allocation, a monthly operational budget of 30,000 USD in HSUITE tokens is required for development sustainability. This approach demonstrates the team's commitment to receiving fair, stable compensation for their work in USD terms, rather than speculating on potential token appreciation. The focus is on sustainable development through predictable monthly funding rather than token holdings.

  • The withdrawal process is fully automated through:

    1. One-time recursive DAO proposal for operational funding (can be modified by future proposals)

    2. Real-time HSUITE/USD price calculation

    3. Automatic conversion of USD amount to equivalent HSUITE tokens

    4. Smart-Node-controlled treasury disbursement

  • The system includes fail-safes:

    • Initial DAO approval required for the recurring monthly withdrawals

    • Price calculation uses a 24-hour TWAP (Time-Weighted Average Price) to prevent manipulation

    • Randomized withdrawal timing within each month for enhanced security against front-running

    • Maximum withdrawal limits in both USD and HSUITE terms

    • Automatic transaction rejection if price feeds are stale or compromised

Dynamic Treasury Allocation

  • The HSUITE Treasury implements a flexible spending model governed entirely by the community through the DAO:

    • Marketing budgets can be adjusted based on community needs and market conditions

    • Special initiatives and partnerships can receive funding through community consensus and/or the HSUITE FOUNDATION

    • Emergency funds can be allocated through expedited proposals when necessary

    • Extended team members (moderators, consultants, advisors) may receive fixed monthly HSUITE allocations based on their roles and contributions. (ex. 625,000 HSUITE/week)

  • The spending process follows a structured approach:

    1. Community/Team members submit detailed spending proposals

    2. Proposals undergo community discussion and refinement

    3. DAO voting determines approval and allocation amounts

    4. Dedicated Smart-Apps automatically execute approved distributions

    5. Real-time tracking and reporting ensure transparency

Smart Node Runner Rewards

Staking Returns

  • Smart Node operators earn an up to 8% Annual Percentage Rate (APR) on their locked HSUITE tokens with a minimum lock period of 1 year.

  • Rewards are automatically distributed to node runners based on their locked amount.

  • Node runners must commit to running their node and keeping their tokens locked for at least 1 year to be eligible for rewards.

  • This mandatory lock period ensures long-term commitment and network stability.

NFT Subscription Model

Developer Access System

  • Developers must acquire NFT subscriptions to access the Smart-Node SDK.

  • Each NFT grants a predetermined allocation of HTTP calls for smart-node interactions.

  • All subscription payments are made in HSUITE tokens.

  • Paid HSUITE tokens are automatically sent to a dedicated burning account.

Deflationary Mechanism

Token Burning Process

  • HSUITE tokens from NFT subscriptions are systematically burned at scheduled intervals.

  • The burning rate correlates directly with developer activity and platform usage.

  • Increased development naturally leads to accelerated token burning.

Ecosystem Growth

Smart-App Marketplace

  • NFT subscription holders can create their own smart-apps.

  • Developers can mint and sell secondary NFT subscriptions.

  • Creates a self-sustaining ecosystem of shared resources and applications.

  • Enables revenue sharing opportunities within the developer community.

PreviousTokenomics v1NextWhat is a Smart Node?

Last updated 5 months ago

Treasury Management
Node Runner Rewards
NFT Subscription Flow
Token Burning Mechanism
Ecosystem Structure