Chapter 5. Performance Verification
Performance Verification
Verification is the core link connecting the digital world and reality. Data must be provided not by humans, but by systems.
5.1 Oracle-Based Automated Verification
The platform uses Chainlink Oracles to import real-world performance data on-chain without manipulation.
Data Source: Trusted Web2 APIs (YouTube, Spotify, KOBIS, etc.)
Verification Node: Decentralized Oracle Nodes cross-validate data
On-Chain Record: Verified result values are recorded in Smart Contracts
5.2 Content Type-Specific Verification Metrics
Different metrics apply depending on the content type.
Movie / Video Content
Box Office Audience
KOBIS (Korean Film Council) API
Daily
Ticket Sales
Distributor Settlement Report
Monthly
OTT Ranking/Views
FlixPatrol / Netflix API
Weekly
Music / Sound Source
Streaming Count
Spotify / Melon / Apple Music API
Daily
Chart Ranking
Billboard / Circle Chart
Weekly
Album Sales
Hanteo Chart
Monthly
YouTube / Web Content
View Count
YouTube Data API
Real-time
Ad Revenue
AdSense Report
Monthly
Subscriber Growth
Channel Analytics
Weekly
5.3 Anomaly Detection System
System to prevent data manipulation (abusing) and ensure fairness.
Spike Detection: Automatic alert if views increase by 500%+ in 1 hour
Bot Filtering: Excluding traffic from specific IP bands
Cross Validation: Compare Views vs Likes/Comments ratio
❌ If Anomaly Detected: Verification Hold → Manual Review → Penalty applied if manipulation confirmed.
5.4 Verification Process Architecture
[Web2 Source] → [Oracle Layer] → [Web3 Layer]
YouTube API, Spotify API, KOBIS Data → Chainlink Node (Aggregation) → Smart Contract (Result Record) → Liquidity Trigger
Last updated