📖
Dev Documents
  • README
  • Basic Concepts
    • TEA Developer Prerequisites
    • The TEA Economic Revolution for Developers
    • The Future of Layer-2s
    • What Makes a Web3 App?
    • Magic of the State Machine
  • Step by Step Tutorial
    • Install Dev Environment
    • Hello World
      • Step 1: Build sample-actor and Run Unit Test
      • Step 2: Start the Local Dev Environment
      • Sample Actor Code Walkthrough
      • Sample Front-end Code Walkthrough
      • 025_understand_request_and_response
    • Deploy Hello World on Testnet
    • Add Login Feature
      • Sample-actor Code Walkthrough - Login Branch
        • tea_sdk_utils
      • Sample Front-end Walkthrough - Login Branch
    • SQL
      • Sample Txn Executor
      • Sample Actor
      • Sample Front-end
    • Reward Fund Transfer
      • Sample Txn Executor
    • Retweet Task
      • Retweet Frontend
      • Retweet Sample Actor
      • Retweet Txn Executor
      • Retweet FAQ
    • Gas Fees
      • Query logs
      • A deep dive into gas measurement and settlement
    • Summary
  • Billing
    • Billing FAQ
    • Gas Fee Billing
    • Gas & Fuse Limits
    • Local Debugging Environment
    • State Maintainer Billing
    • TApp Billing
  • Example TApps
  • Advanced TApps
    • TEA Party TApp Intro
    • TEA Party Code Walkthrough
  • Functions
    • Actors vs Functions
    • Function Calls Between Native & Wasm
    • Native vs Wasm Functions
  • Glossary
    • Actor
    • Adapter
    • App AES Key
    • AuthKey
    • back_end_actor
    • Birth Control
    • Blockchain Listener
    • Capability
    • CML Auctions
    • Commands
    • Consensus
    • Context
    • Conveyor
    • Conveyor: Mutable vs Immutable
    • enclave
    • Followup
    • Front-end
    • GlueSQL
    • GPS
    • Hosting Actor Handlers
    • Hosting CML
    • hosting_profitability
    • Magic of WASM
    • mini-runtime
    • OrbitDb
    • Order of Txns
    • party-actor
    • party-fe
    • Party-state-actor
    • Providers
    • Public Service
    • queries
    • Remote Attestation
    • Staking to Hosting CML
    • Staking to TApp
    • State
    • State Machine
    • State Machine Actor
    • State Machine Replica
    • TEA ID
    • TPM
    • Transactions
    • VMH - Virtual Messaging Hub
    • Where Messages are Stored
Powered by GitBook
On this page
  1. Glossary

Birth Control

Previousback_end_actorNextBlockchain Listener

Last updated 2 years ago

The ecological balance

The TEA Project ecosystem has an ecological balance between computing resource supply in the form of CML and computing resource demand in the form of TApps. CMLs represent the computing supply as CML nodes are capable of executing computing tasks within their protected . TApps represent the demand for these resources as they're the apps that consume computing services.

The DAO monitors the usage (idle time and waiting time) of every CML. If the majority of CML are waiting, it means supply is over demand. If the majority of CML are busy but the TApps have tasks waiting in line to be executed, then that means demand exceeds supply.

Based on the supply/demand ratio, the DAO will automatically increase or decrease the amount of new CML seeds released to the marketplace.

Another indicator for computing supply and demand on the network is the price of CML as reflected in the auction marketplace. If the auction price is too high, the DAO should increase the CML seeds supply (and reduce the supply if prices are too low).

The adjustment on CML supply is made through the DAO governance. Any of these determining factors can be changed by DAO voting. During the first two years of the TEA Project's operation, the DAO is not mature enough and the community is not big enough for voting. During this early stage, the project team will control the birth rate of CML. After 2 years, the DAO will take over the birth rate control programmatically based on the supply and demand factors mentioned above.

enclaves