Profitability of TEA Ecosystem Participants

There are multiple ways of achieving profitability in the TEA ecosystem. Being an investor in TApp or CML bonding curve tokens is one way to earn TEA value. But a more active way is to actually engage in the TEA ecosystem in one of the three following ways.

Profitability Calculations for TEA Ecosystem Participants

Become a Hosting Node Miner

  • Hosting node miners earn gas fees from end users utilizing TApps on their hosting nodes.
  • Initial support is provided through Universal Basic Income (UBI) from the DAO Reserve during the early stages.
  • Miners have the option to subscribe to a state update service, ensuring faster state machine updates, with an associated subscription fee.
  • Miners are responsible for the maintenance costs of their hosting node machines, typically requiring Amazon Nitro hardware.
  • To operate on the TEA network, miners must acquire CML seeds (NFTs) serving as licenses for their hosting nodes.
Gas fees are measured through the TEA Project mini-runtime virtual machine's billing system, based on WebAssembly code execution. Comparable to Ethereum's ETH gas system but more cost-effective, miners earn higher profits as more users visit their hosting nodes, leading to increased code execution and gas fees.
During periods of low user activity, UBI from the DAO Reserve subsidizes miners, helping cover hosting node maintenance costs.
The state subscription fee is initially waived. When real-time state updates become available for hosting nodes, this fee will be implemented. This feature is especially relevant to applications like real-time collaboration applications.
Hosting node revenue contributes to CML bonding curve tokens, with a percentage (theta %) directly benefiting the miner. This revenue-sharing design extends to CML bonding curve investors as dividends, establishing a symbiotic relationship. Investor support enhances the market cap of CMLs, improving their ranking and visibility, attracting more end user attention and traffic for miners.
  • Early TEA Mining Opportunity: Optimize profitability by joining TEA mining at the earliest opportunity. A reduced number of hosting miners correlates with higher Universal Basic Income (UBI).
  • Strategic CML Bonding Curve Creation: When establishing your CML bonding curve, allocate substantial funds during the initial funding phase, as prices are lower. A higher market cap secures a superior rank, enhancing competition and attracting more users and traffic.
  • Cost-Effective Amazon Nitro Machine Selection: Choose an Amazon Nitro machine with an ARM CPU for cost efficiency, as they generally offer lower prices compared to X86 CPUs.
  • Monitoring Hosting Node Status: Stay vigilant about the status of your hosting nodes. While they typically undergo automatic upgrades, manual restarts may be necessary to ensure synchronization with the latest version. An outdated hosting node risks suspension, resulting in income loss during downtimes.

Become a TApp developer

  • TApp developers are relieved of server costs as miners cover their own machine expenses.
  • Revenue for TApp developers is generated through in-app purchases made by end-users, determined by the payment logic design in your app.
  • When TApps initiate transactions with the state machine or store data in the global state, associated costs are borne by the TApp and paid to state maintainer nodes. This expense is calculated using the TEA Project mini-runtime billing system and a memory tax algorithm.
  • Each TApp functions as a bonding curve token, with generated revenue directly contributing to the bonding curve token, akin to the revenue model for hosting miners.
Besides the general strategies mentioned earlier, there are some specific considerations for developers:
  • Optimize Client-Side Logic: Adhere to the "no-free-lunch" rule by handling application logic on the end user's client side (browser or mobile app) whenever possible. Logic executed on the client side incurs no charges. Conversely, if the logic is processed on the hosting node (server side), the end user is responsible for the associated gas fees. When sending transactions to the state machine or storing data in the state machine, your app incurs gas fees and memory taxes, emphasizing the importance of designing with overall user and cost efficiency in mind.
  • Hierarchical Data Storage Approach: Prioritize storing data first in the client, then in the hosting node, and finally in the state machine. Storing data in clients (browser or mobile app) has no associated cost, while storing data in the state machine incurs memory taxes. Hosting nodes can sometimes store data at a lower cost without synchronizing with the state machine, although this approach may be less secure.
  • Protocol-Based Design Over Server Logic: Consider designing protocols for business logic that can be executed between clients, eliminating the need to send transactions to the server or state machine. Payment channels like the Lightning Network exemplify this approach.
  • Limited Server Access for Logs: In the Web3 environment of the TEA Project, developers lack access to miners' machines, and the project is designed to prevent the disclosure of confidential runtime information from inside the enclave. Unlike the Web2 world, where developers commonly access server logs for debugging and monitoring, this is not feasible in TEA Project Web3. Developers must design their own logic for log outputs, ensuring the code is open for public review to avoid inadvertent disclosure of confidential data. Additionally, note that even miners can only access server logs generated outside the enclave.

Become a State Maintainer: Own Your SEAT

The TEA Project relies on a minimum of three state machine nodes to uphold the system's state, often referred to as the ledger in the blockchain domain.

Limited Number of State Machine Nodes

To ensure efficient transaction processing, a finite number of state machine nodes are required at any given time. An excess of nodes may impede transaction speed. Managing a state machine demands specialized expertise beyond the capabilities of every miner. During the initial phase of the TEA Project, the core team will oversee all state machine nodes until the system achieves stability for public hosting. Meanwhile, community members can participate in the SEAT competition to share the state machine revenue. Each state machine node is associated with a SEAT, representing its financial status. The SEAT owner is entitled to all revenue generated by the node after covering its associated costs.

Revenue Generation from State Machine Nodes

Transactions submitted to the state machine incur a gas fee, dependent on their computation resource consumption. TApps storing data in the state are subject to a memory tax based on occupied data size and remaining free memory. Both gas fees and memory taxes are distributed evenly among active state machine nodes.
The memory tax rate is not a flat rate; it varies based on the amount of remaining free memory. The less free memory available, the higher the tax rate applied. As more TApps utilize the limited state memory, the escalating cost serves as an incentive for TApp developers to optimize their memory usage.

Costs Associated with State Machine Nodes

Running a state machine requires an Amazon Nitro machine, with rental fees paid in FDUSD to Amazon AWS. SEAT owners are responsible for covering these expenses during their ownership period. To ensure fairness among community members, a Harberger TAX, equivalent to 7% of a self-estimated price, is levied on each SEAT owner. This tax contributes to the DAO Reserve pool. ## SEAT Auction Individuals aspiring to own a SEAT can participate in the SEAT auction through the Harberger TApp. The highest bidder for a SEAT, determined by their self-estimated price, wins ownership during the next settlement window. Upon transfer of ownership, the new SEAT owner commences payment of AWS rental in FDUSD and the Harberger TAX, concurrently gaining access to revenue generated by the node.
Owning a SEAT is a straightforward process, requiring no technical background. The primary adjustable element is the self-estimated price of the SEAT.
  • While offering a higher self-estimated price can safeguard your SEAT from competitors, it also results in a higher Harberger TAX. Remember, the Harberger TAX is fixed at 7% of your self-estimated price.
  • Regularly monitor your FDUSD balance, as the system's cron job transfers AWS rental FDUSD every few hours. If your balance is in overdraft, you will automatically lose the SEAT. Additionally, the SEAT's self-estimate price resets to 1 TEA. Notably, in this scenario, your SEAT will be forced to sell at the fixed price of 1 TEA, potentially lower than your initial purchase price.
  • Due to the Harberger TAX, owning a SEAT does not guarantee constant profitability. Intense competition for SEATs may drive up self-estimate prices to a level where the combined Harberger TAX and rental costs exceed revenue. In such cases, you have the option to lower your self-estimated price for someone else to take over or completely relinquish the SEAT. Surrendering your SEAT is equivalent to selling it at 1 TEA to the DAO Reserve account.
  • Regularly check the Harberger TApp; you might encounter excellent deals when someone inadvertently loses their SEAT due to overdraft, offering the SEAT at the minimal price of 1 TEA!
Last modified 1mo ago