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 0x43ce265f41589eb59aedbb2ba3060b5b3b302663202b9b099f1a3689ef0e37e0. Chain 2 (Bitcoin): anchored in block 953770 (2026-06-15T09:50:11Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/c0d3235c-2d9b-4e73-aeb2-a92e055c5705.json and https://artists.proofprofile.net/proofs/artist/c0d3235c-2d9b-4e73-aeb2-a92e055c5705.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Teu sim, mas não. (feat. Mariana Nolasco & Pedro Calais)
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 0x9745ac4838097987c43bdd40fdf17899352baa7b1cba50590070ee0588db0526. Chain 2 (Bitcoin): anchored in block 953515 (2026-06-13T12:53:06Z), 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/BXBMG2200165.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9745ac4838097987c43bdd40fdf17899352baa7b1cba50590070ee0588db0526. Chain 2 (Bitcoin): anchored in block 957043 (2026-07-07T13:52:39Z), 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/BXBMG2200165.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x6c898f7d933cf872ca2030a98fe13def6fccdd8b9fc6d302157a16cba0126593. 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/BRFFP1800025.
Vitor Kley e Pedro Calais Falam Sobre Detesto Despedidas
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3f92d9b2561c4c3221ae670653c20cfd4cfd2367c4225b671c8cb27d7f962323. 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/BR3751900172.