Rename may refer to: Rename (computing), rename of a file on a computer RENAME (command), command to rename a file in various operating systems Rename (relational algebra), unary operation in rela
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 0x5fd5baaeed5ab035af9a9d425bb1022227f5229ea5b52e332fccd741c9546ccd. Chain 2 (Bitcoin): anchored in block 953980 (2026-06-16T17:16:51Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/2b7b160f-a746-4810-ae25-29ba774e97b9.json and https://artists.proofprofile.net/proofs/artist/2b7b160f-a746-4810-ae25-29ba774e97b9.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 0xd419cb20976a2c580a1fd3cced1b047dc710a3a9b8e9fdbca3e215346db30d5b. Chain 2 (Bitcoin): anchored in block 958430 (2026-07-17T15:33:28Z), 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/JP92G2518681.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc5aea177f249e38b02d4acb6dcb974493eacca4ee986febfa5577929df825dfe. Chain 2 (Bitcoin): anchored in block 959132 (2026-07-22T13:20:46Z), 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/JP92G2518682.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x240e9c493f360bf33ffd0e99a98f47d2813ad8b170b91a6280277d625fabc26c. Chain 2 (Bitcoin): anchored in block 956634 (2026-07-04T10:04:33Z), 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/JP92G2518679.