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 Note: an OTS proof may carry multiple Bitcoin attestations; OTSBitcoinBlock is the earliest confirmed one — a later attestation inside the proof corroborates it and is not a mismatch
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x845f98ca53ed6755789f813dc72a90be655a25a9f5f143fb804b3499aff44374. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/f185add2-52fe-4cf6-89b9-185a8dd6920b.json and https://artists.proofprofile.net/proofs/artist/f185add2-52fe-4cf6-89b9-185a8dd6920b.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
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 Note: an OTS proof may carry multiple Bitcoin attestations; OTSBitcoinBlock is the earliest confirmed one — a later attestation inside the proof corroborates it and is not a mismatch
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0f24202768bbe8b7736e2f7b1643d919abb40be79e3550a91a071e7d17cd5a8d. Chain 2 (Bitcoin): anchored in block 956302 (2026-07-02T03:30:09Z), 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/JPCO02329260.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xddb78b252db6acc55e0cd4e5c00eb1a3618d1814ae3c86da9813a7e7e073a844. Chain 2 (Bitcoin): anchored in block 960175 (2026-07-30T00:16:15Z), 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/JPCO02329290.
ハッピー☆ブギ - オリジナル・カラオケ
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9830f40aaeec0d5288e24aa10d4c629dca40e025b8310d0c48b5efb9c717fc77. Chain 2 (Bitcoin): anchored in block 960397 (2026-07-31T12:24:41Z), 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/JPCO02329269.
東京ブギウギ - オリジナル・カラオケ
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0a79c82f9bdb3bc57cd275d02d187f3f0b6e6bea732537751ab8f71fa0c972a5. Chain 2 (Bitcoin): anchored in block 960494 (2026-08-01T01:44:32Z), 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/JPCO02329299.