Skip to main content

Content Types

Overview

SuiVerse supports various forms of learning content to provide a comprehensive educational experience.

Global Tag System

All content types share a unified tag system enabling cross-content discovery.

struct Tag has key, store {
id: UID,
name: String,
description: String,
parent_tag: Option<ID>,
created_by: address,
status: u8, // 0: Pending, 1: Active, 2: Deprecated
usage_count: u64,
governance_proposal_id: ID
}

Tag Hierarchy

  • Parent Tags: Major categories (e.g., Blockchain, DeFi, NFT)
  • Child Tags: Detailed classifications (e.g., Sui, Move, Smart Contract)
  • Auto Suggestions: AI-based tag recommendations

1. Articles

Original Articles

Educational content created directly by authors

struct OriginalArticle has key, store {
id: UID,
title: String,
author: address,
content_hash: vector<u8>, // IPFS hash
tags: vector<ID>,
view_count: u64,
earnings: Balance<SUI>,
status: u8,
deposit_amount: u64,
validator_reviews: vector<ValidationReview>
}

Features

  • IPFS Storage: Optimized for large content
  • Validation Required: Requires approval from 3 validators
  • Revenue Generation: 0.001 SUI per view

External Articles

Curated external links

struct ExternalArticle has key, store {
id: UID,
title: String,
recommender: address,
url: String,
description: String,
preview_image: String,
tags: vector<ID>,
view_count: u64,
earnings: Balance<SUI>
}

Features

  • Link Curation: Share valuable external resources
  • Low Entry Barrier: 0.5 SUI deposit
  • Community Contribution: Recommender rewards

2. Projects

Hands-on learning through ecosystem projects

struct CuratedProject has key, store {
id: UID,
title: String,
curator: address,
project_url: String,
description: String,
tags: vector<ID>,
view_count: u64,
earnings: Balance<SUI>
}

Project Types

  1. Open Source Projects: GitHub repositories
  2. Tutorial Projects: Step-by-step learning
  3. Template Projects: Reusable code

Curation Criteria

  • Code quality
  • Documentation level
  • Educational value
  • Practicality

3. Quizzes

Transformable assessment content

struct Quiz has key, store {
id: UID,
creator: address,
encrypted_content: vector<u8>,
difficulty: u8,
category: String,
tags: vector<ID>,
usage_count: u64,
variation_count: u64,
earnings: Balance<SUI>
}

Quiz Features

  • 100% On-chain: Complete decentralization
  • Encrypted Security: Original never exposed
  • Automatic Variation: 6 variation algorithms
  • Usage-based Revenue: 0.02 SUI per exam usage

Content Validation System

All content must go through validator review.

Unified Validation Structure

struct ContentDeposit has key, store {
id: UID,
content_id: ID,
depositor: address,
amount: u64, // DAO가 콘텐츠 타입별로 관리
content_type: u8, // 1: OriginalArticle, 2: ExternalArticle, 3: Project, 4: Quiz
status: u8 // 0: Locked, 1: Returned, 2: Forfeited
}

struct ValidationReview has store {
validator: address,
content_id: ID,
score: u8, // 0-10
criteria_scores: vector<CriteriaScore>,
decision: u8 // 1: Approve, 2: Reject
}

Validation Configuration

struct ValidationConfig has key {
id: UID,
// 콘텐츠 타입별 승인 기준 (거버넌스로 관리)
article_approval_threshold: u8, // 예: 7/10
project_approval_threshold: u8, // 예: 7/10
quiz_approval_threshold: u8, // 예: 8/10

// 타입별 검증자 수
article_validator_count: u8, // 예: 3명
project_validator_count: u8, // 예: 5명
quiz_validator_count: u8, // 예: 3명

// 타입별 선택 방식
article_selection_method: u8, // 1: Random, 2: Expertise-based
project_selection_method: u8, // 1: Random, 2: Expertise-based
quiz_selection_method: u8, // 1: Random, 2: Expertise-based

last_governance_update: ID // 마지막 거버넌스 제안 ID
}

Content Creation Flow

Content Revenue Model

Revenue Structure

Content TypeView RewardUsage RewardQuality Bonus
Original Article0.001 SUI-0.01 SUI (rating >4.5)
External Article0.0005 SUI--
Curated Project0.0008 SUI-0.005 SUI (completion rate)
Quiz-0.02 SUI/exam0.05 SUI (top 10%)

Revenue Maximization Strategy

  1. Create High-Quality Content: Earn quality bonuses
  2. Use Appropriate Tags: Increase discoverability
  3. Regular Updates: Maintain relevance
  4. Community Engagement: Build reputation

Content Lifecycle

Creation → Validation → Activation → Monetization → Update

  1. Creation Phase: Initial content writing
  2. Validation Phase: Community validation (48-72 hours)
  3. Activation: Platform publication
  4. Monetization: View/usage-based revenue
  5. Update: Continuous improvement