ACP-coin Docs
  • Table of Contents
  • 1. Introduction to the Project
    • 1.1 Project Overview
    • 1.2 Mission and Vision
    • 1.3 Core Value Propositions
    • 1.4 Recognition of Market Problems
  • 2. Technical Architecture & the RSR System
  • 2.1 Prime Mining Architecture
  • 2.2 Mining DApp Features & User Flow
  • 2.3 Participatory Hybrid Mining
  • 3. Token Economy
  • 3.1 Definition and Utility of the ACP Token
  • 3.2 Token Supply and Distribution Model
  • 3.3 Token-Based Reward Circulation
  • 3.4 Circulation Stabilization & Lock-up Policy
  • 4. Reward & Participation Framework
  • 4.1 Dual Staking Model (Passive / Active)
  • 4.2 Trine Scoring Model™ – Contribution Quantification
  • 4.3 Incentives and Tier-Based Rewards
  • 5. Ecosystem Expansion Strategy
  • 5.1 Utility Based on Real Computing Power
  • 5.2 Local Node Ecosystem Model
  • 5.3 Compute-as-a-Service (CaaS)
  • 5.4 Community-Oriented Contribution Services
  • 6. Roadmap
  • 6.1 Governance Evolution & Operational Structure
  • 6.2 Quarterly Execution Plans
  • 7. Disclaimer
Powered by GitBook
On this page

5.3 Compute-as-a-Service (CaaS)

ACP’s service layer will evolve into a Compute-as-a-Service (CaaS) architecture. Various user groups can access compute resources through token-based transactions or partnerships.

User Type

Purpose

Usage Model

Revenue Flow

AI Startups

LLM inference, fine-tuning

Tiered API plans

ACP payments split to contributors

Content Creators

Video/image generation

One-time API calls

Direct ACP consumption

Educational Institutions

Research, training

Partnership or grant model

Brand value and contributor onboarding

Previous5.2 Local Node Ecosystem ModelNext5.4 Community-Oriented Contribution Services

Last updated 24 days ago