1. Compute SHA-256 of OTSCanonicalRecord value → must equal OTSHash 2. Open OTSProofURL → extract Bitcoin block number → must equal OTSBitcoinBlock 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Read CopyrightID inside OTSCanonicalRecord → must equal the CopyrightID above 5. GET OTSVerificationAPI → pre-computed 6-check result from server 6. If all match: this entity was registered on CopyrightChains at OTSTimestamp, independently verifiable on Bitcoin
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa39ff105d842d8b42352697e9331047450129662351fc36c05c5ae7e7dbfc6be. Chain 2 (Bitcoin): anchored in block 953408 (2026-06-12T19:28:13Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/350c26e6-3895-494b-b807-129c0b4ed428.json and https://artists.proofprofile.net/proofs/artist/350c26e6-3895-494b-b807-129c0b4ed428.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
red swan but it's lofi (attack on titan)
youseebiggirl but it's lofi (attack on titan)
identity but it's lofi (the promised neverland)
call your name but it's lofi (attack on titan)
vivid vice but it's lofi (jujutsu kaisen)
name of love but it's lofi (attack on titan)
blue bird but it's lofi (naruto shippuden)
cry baby but it's lofi (tokyo revengers)
tokyo wonder but it's lofi (tokyo revengers)
nezuko's theme but it's lofi (demon slayer)
sadness and sorrow but it's lofi (naruto)
crossing field but it's lofi (sword art online)
akuma no ko but it's lofi (attack on titan)
one summer's day but it's lofi (spirited away)
orange but it's lofi (your lie in april)
kizuna no kiseki but it's lofi (demon slayer)
bling bang bang born but it's lofi (mashle)
run sakamoto run but it's lofi (sakamoto days)
1. Confirm isrcCode identifies the recording in the pre-2022 source corpus and cc-db-prod record 2. GET OTSVerificationAPI → server-side canonical-record, hash, and attestation checks must pass 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Confirm CopyrightID is the CopyrightChains transaction hash 5. If all match: the cc-db-prod record is independently anchored on Bitcoin at OTSTimestamp
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x29731832d9bded2522c63f5e482221950119cb2bc85cc2b4a7841667312b1b35. Chain 2 (Bitcoin): anchored in block 958388 (2026-07-17T09:14:21Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZMEQ2597013.
ao no sumika but it's lofi (jujutsu kaisen)
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1924d752b0c891cfc078dd15d242e2723141f5eeb36b2a082346d25f12b039f4. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZTBB2571941.