Hokusai User Personas
This document outlines the key user personas in the Hokusai ecosystem and their specific needs, goals, and use cases.
Data Suppliers
Data Suppliers are organizations or individuals who contribute high-quality data to improve AI models in the Hokusai ecosystem.
Profile
- Who: Companies, research institutions, or individuals with valuable datasets
- Goals:
- Earn tokens by contributing data that improves model performance
- Monetize their data assets
- Ensure privacy and compliance in data sharing
- Technical Requirements:
- Ability to format data according to Hokusai standards
- Understanding of data quality metrics
- Basic knowledge of AI model performance metrics
Use Cases
-
Dataset Contribution
- Submit new datasets for model training
- Earn tokens based on performance improvements
- Track contribution impact through DeltaOne rewards
-
Data Quality Management
- Validate data format and quality
- Monitor data usage and impact
- Maintain data privacy standards
Model Developers
Model Developers are AI engineers or researchers who create, improve, or integrate models into the Hokusai ecosystem.
Profile
- Who: AI researchers, ML engineers, or organizations with AI models
- Goals:
- Launch new models on the platform
- Improve existing models with new data
- Earn tokens through model usage and improvements
- Technical Requirements:
- Expertise in AI/ML development
- Understanding of model evaluation metrics
- Knowledge of smart contract integration
Use Cases
-
Model Deployment
- Register new models on the platform
- Set performance baselines
- Configure token economics
-
Model Improvement
- Integrate new training data
- Monitor performance improvements
- Earn DeltaOne rewards for enhancements
Investors
Investors participate in model token launches, trade on the bonding curve AMM, and benefit from AI model performance and API revenue.
Profile
- Who: Individual investors, crypto funds, or organizations seeking AI-backed assets
- Goals:
- Invest in promising AI models during launch period
- Trade tokens on the CRR bonding curve AMM
- Benefit from API fee deposits to reserves
- Support ecosystem growth and innovation
- Technical Requirements:
- Understanding of CRR bonding curves
- Knowledge of AMM mechanics (buy/sell dynamics)
- Familiarity with smart contracts and DeFi
- Crypto wallet and USDC holdings
Use Cases
-
Launch Period Participation
- Research models before seven-day bonding round
- Buy tokens during buy-only period (Days 0-6)
- Dollar-cost average across launch period
- Monitor reserve growth and community engagement
- Complete Guide →
-
Secondary Trading
- Buy tokens post-launch (Day 7+)
- Sell tokens on AMM for USDC
- Time entries/exits based on API fee deposits
- Monitor price dynamics and reserve changes
- Buy Guide → | Sell Guide →
-
Portfolio Management
- Diversify across multiple model tokens
- Balance position sizes based on risk tolerance
- Take profits at predetermined targets
- Implement stop-loss strategies
- Track performance metrics
-
Fundamental Analysis
- Evaluate model performance and improvement trajectory
- Assess API usage and revenue generation
- Monitor fee deposits to USDC reserves
- Track token minting and burning events
- Analyze community growth and engagement
Investment Strategies
Conservative:
- Invest in mature models with proven API revenue
- Higher CRR tokens (35-50%) for stability
- Hold long-term (90+ days)
- 1-5% portfolio allocation
Moderate:
- Mix of launch and mature models
- Medium CRR tokens (20-35%)
- Medium-term holds (30-90 days)
- 5-15% portfolio allocation
Aggressive:
- Focus on early launches and high-growth models
- Lower CRR tokens (10-20%) for upside
- Short to medium-term (7-30 days)
- 15-30% portfolio allocation
Key Resources for Investors
- Investor Guide - Complete investment playbook
- Launch Period - Seven-day bonding round details
- AMM Overview - How the bonding curve works
- Bonding Curve Math - Price formulas and examples
Getting Started
Each persona can begin their journey with Hokusai through these key resources:
For detailed information about specific workflows and requirements, please refer to the relevant sections in the documentation.