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 0xe222b72fdc8ca403ccd04f2e4277773376b953264fd9eb1cee9f61f898a8a730. Chain 2 (Bitcoin): anchored in block 954066 (2026-06-17T08:11:48Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/69cdbccc-1f8b-4c2f-b10b-b7dd17fdf876.json and https://artists.proofprofile.net/proofs/artist/69cdbccc-1f8b-4c2f-b10b-b7dd17fdf876.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
CREO QUE HOY NO ME APETECE QUERERME MORIR
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 0x03ba60c6af213ff20a6a84b969510691df551082f63fbeaf578e1a3c97fb3c3a. Chain 2 (Bitcoin): anchored in block 954130 (2026-06-17T19:07:14Z), 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/BK4DA2214551.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa777806007c4f6ae0dd4da3e1344cc7c0ddeb3a00031d9fe2aac826cae6e7f8a. 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/BK4DA2214552.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc7cd09c2dcc6c5b331d1d3b4e08c83c6fdb0c52829a4a8beaa99e87acf8d6f4f. Chain 2 (Bitcoin): anchored in block 956312 (2026-07-02T05:09:12Z), 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/BK4DA2307089.
¿DEBERÍA ESTAR CONTENTO DESPUÉS DE VERTE?
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xfc6fcc353c6ba1dc703323476d03c6617028b7fb0308bcf35619b0aa52bb9de0. Chain 2 (Bitcoin): anchored in block 956351 (2026-07-02T11:38:34Z), 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/BK4DA2307091.