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 0x760e9fb269d23bbb8f39bc46f9f2f7e279c547f96103c6096c8d2fc7ad3eb5a2. 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/8d3837ff-34d4-49e9-bc06-7869d1eff630.json and https://artists.proofprofile.net/proofs/artist/8d3837ff-34d4-49e9-bc06-7869d1eff630.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 0xffea800e6c2668cb3595802b330896233493058271e038b1b6c64b77387b42e6. Chain 2 (Bitcoin): anchored in block 956639 (2026-07-04T11:19:20Z), 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/QZTAS2369376.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1528ff513ae28ea9ac1c087757bdc08d61ff0929ccc7f5ed6ac1401f43af1177. Chain 2 (Bitcoin): anchored in block 958392 (2026-07-17T09:46:31Z), 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/QZTB52313614.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xcbb3eaa415e8d3216e18ada3b937efb588210ac5bd48c7f2a54d53b0b2d7f9db. Chain 2 (Bitcoin): anchored in block 958300 (2026-07-16T16:14:30Z), 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/QZWFQ2309428.
Why U Texting? (Remix feat. 比尔牛 lil slower)
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8c3ca47f5cf96e0c9250e86098c664e973975e7702ce7fcdb203da785b36021e. Chain 2 (Bitcoin): anchored in block 958051 (2026-07-14T19:14:42Z), 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/QZZ782496453.