In folklore, a revenant is a spirit or animated corpse that is believed to have been resurrected to haunt the living. The word revenant is derived from the Old French word (see also the related Fren
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 0x6911d71004a1db983cae36f616437f0811864e61fb47876d35c808e8f06c4520. Chain 2 (Bitcoin): anchored in block 953812 (2026-06-15T17:06:52Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/f725a853-cdf1-420c-8910-e12ee6856ca2.json and https://artists.proofprofile.net/proofs/artist/f725a853-cdf1-420c-8910-e12ee6856ca2.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 0x46b67778415179bab2137ba950a378a00b0bac5c08bb321eef565875b59664b2. Chain 2 (Bitcoin): anchored in block 958897 (2026-07-20T14:57: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/SEUM71800720.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x7fba850444c103b5a1414fc6f2bf2d6c25cf9bfba12e96b5c70a000880c025e7. Chain 2 (Bitcoin): anchored in block 957880 (2026-07-13T16:39:18Z), 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/QZDA82137899.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc4b63001de113009379814dc02786e6edb798b0d4d44ea8db084357273b45bbb. Chain 2 (Bitcoin): anchored in block 960138 (2026-07-29T19:35: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/QZMHN2030391.