Oracle
Copyright Metadata Oracle
Overview
The BeatSwap Oracle permanently records structured copyright metadata for music on the blockchain. It serves as the core foundation of the BeatSwap ecosystem, providing the trusted source of truth for all services including Space, RWA Launcher, and Music DEX (BeatSwap).
Beyond simple data storage, the Oracle offers accurate and real-time verifiable copyright information to BeatSwap internal services and approved external partners (such as streaming platforms and licensing agencies).
Additionally, through the Oracle, rights holders can monitor the real-time usage and royalty generation of their music assets transparently.
Key Features
✅ On-Chain Metadata Storage
Permanently stores detailed information (title, composer, lyricist, arranger, genre, work type, publisher, unlock count) and rights holder addresses in the ICP Canister.
Rights holder addresses are updatable, and all changes are permanently recorded to ensure full historical traceability.
All metadata is managed based on a standardized schema.
✅ Real-Time Verification and Query
Enables immediate metadata retrieval through HTTP or authenticated Canister interfaces.
Designed to support compatibility across both Web2 and Web3 services.
✅ Multi-Blockchain Integration
Stores token addresses, staking contract addresses, and contract versioning without dependency on specific blockchains.
Supports seamless interoperability and rights tracking across networks.
✅ Real-Time Usage Recording
Copyright usage events (such as streaming activity) are recorded and linked to corresponding works in real time.
Enables accurate, tamper-proof tracking of royalties and work performance metrics.
Data Structure
The Oracle organizes metadata into five major categories:
music_work_info
Title, composer, lyricist, arranger, genre, work type, publisher, unlock count.
production_info
Main artist, musician, record label, release date, playback duration.
daily_rights_holders
Daily recorded addresses for copyright and neighboring rights holders.
tokenized_right_contracts
Mapping of token contract addresses for copyright and neighboring rights.
verification_contracts
Metadata of deployed staking contracts including address, version, and deployment date.
All metadata fields are implemented using Motoko type definitions, ensuring native compatibility with Internet Computer smart contracts.
Metadata Flow
Registration: Musicians register their music metadata through the RWA Launcher platform.
Validation: Submitted metadata undergoes schema-based validation to ensure structural integrity.
Storage: Once validated, metadata is permanently recorded in the Core Canister.
Query: BeatSwap services and approved external partners can access and retrieve metadata in real time.
Rights holders can continuously track ownership changes, royalty-generating usage events, and real-time performance of their assets.
External Integrations
🎧 External Streaming and Partner Platforms
Verified metadata can be fetched and displayed inside external services.
Approved Partner IDs can use the Primary Key of songs to smoothly identify rights holders and validate ownership.
💰 Royalty Settlement Support
BeatSwap internal services and approved Partner IDs can query daily rights ownership and usage activity data.
Enables transparent and accurate royalty distribution based on verifiable blockchain records.
Summary
Storage
Internet Computer Canister (Core Oracle)
Usage
BeatSwap internal services, external streaming and licensing partners
Real-Time Query
✅ via @dfinity/agent SDK or HTTP API
Blockchain Integration
✅ Token addresses and contracts stored without network dependency
Rights Tracking
✅ Daily ownership changes and real-time usage history
Royalty Transparency
✅ Rights holders can verify royalty generation in real time
Technology Stack
Motoko + HashMap + Principal Mapping + Canister APIs
Last updated