[Showcase] BeatSwap — IP-Rights Oracle and Licensing-to-Earn on ICP

Developers Showcase
1

[Showcase] BeatSwap — IP-Rights Oracle and Licensing-to-Earn on ICP

TLDR

BeatSwap builds an on-chain Oracle on the Internet Computer that verifies, timestamps, and stores IP-Rights metadata, enabling transparent royalty tracking and cross-chain licensing. We are turning music and broader IP-Rights into verifiable RWA with community engagement and decentralized trading.

What we built with the ICP Developer Grant

Through the grant, we shipped Oracle Core canisters that:

  • Verify and timestamp IP-Rights events on ICP

  • Register and serve canonical metadata for creators, rights holders, and licensed works

  • Produce deterministic snapshots that downstream systems can use for rewards and settlement

  • Expose read APIs for dashboards, explorers, and cross-chain bridges

This foundation enables automated licensing validation and royalty accounting for IP-Rights tokenization on other chains.

Why it matters

Web2 licensing is fragmented and opaque. Rights ownership, usage events, and payouts are scattered across private databases, making audits and revenue sharing slow and difficult. BeatSwap’s Oracle makes these records verifiable on-chain, so creators and fans can trust the numbers and settle faster.

Key achievements and traction

  • 330,000+ users

  • 3,000,000+ total transactions, averaging 100,000 per day

  • Operational Oracle Core canisters with read endpoints for external indexers

  • Cross-chain design for IP-Rights tokenization and settlement

How it works

  1. IP-Rights Intake
    Creators and rights holders register works and rights splits. Off-chain evidence and signatures are anchored via canister calls.

  2. On-chain Registry
    Oracle canisters validate inputs, timestamp them, and store normalized metadata and event logs on ICP.

  3. Snapshots and Proofs
    The Oracle emits monthly snapshots for reward distribution and provides proofs that downstream systems can verify.

  4. Cross-chain Settlement
    Bridges and partner modules consume Oracle data to mint or update RWA representations and to distribute licensing rewards.

Technical architecture (high-level)

  • Canister set

    • Registry canister: normalized IP-Rights records, identifiers, splits

    • Events canister: usage logs, licensing actions, accrual references

    • Snapshot canister: deterministic monthly snapshots and proofs

  • Interfaces

    • Query methods for dashboards, explorers, and partner chains

    • Batch endpoints for indexers and data exports

  • Data model

    • Work, Right, Party, Split, UsageEvent, Snapshot

Repos and resources

GitHub (Oracle Core): https://github.com/beatswap-labs/oracle-core

Live demos and screenshots

  • Oracle Front (ICP Canister Read Demo)

  • Dashboard preview with IP-Rights records and usage events

    oracle
    oracle1920×1198 182 KB

Roadmap

  • Q4 2025: Oracle – Licensing-to-Earn
    Launch of the Oracle-powered Licensing-to-Earn system, enabling verified IP usage and transparent royalty distribution on-chain.

  • Q4 2025: Oracle – Vault-to-Earn
    Integration of Vault-based Time-Weighted Average Balance (TWAB) rewards linked to IP licensing data recorded on the Oracle.

  • Q1 2026: PoR (Proof of Rights) System & Space
    Deployment of the Proof-of-Rights module to verify and stake ownership of tokenized IP-Rights across multiple chains.
    Introduction of “Space,” a social hub for creators and fans to collaborate, license, and earn directly within the BeatSwap ecosystem.

  • Q2 2026: RWA Launcher & RWA DEX
    Launch of the RWA Launcher for IP tokenization and a decentralized exchange (DEX) for IP-Rights trading and liquidity.

What we are asking from the community

  • Feedback on our canister interfaces and data schema

  • Suggestions for additional fields that would help your use case

  • Builders who want to consume Oracle snapshots for analytics, payouts, or tokenization modules

Team

A cross-functional team of engineers and operators focused on IP-Rights RWA, multi-chain infra, and creator tooling.

Get involved

  • Comment with integration ideas and data requirements

  • Tell us which SDK language you want first

  • If you are building creator tools or music platforms, let’s talk

Thanks for reading. We would love your feedback and are happy to answer technical or product questions in the thread.