Repulsion may refer to: Disgust, or repulsion, an emotional response to something considered offensive or unpleasant Repulsion, a type of genetic linkage Repulsion in physics, Coulomb's law Repul
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 0x9f9fe8d16a5be9287d0489787846f3451daf7f5f3265fcf0d47cca31e107c296. Chain 2 (Bitcoin): anchored in block 953947 (2026-06-16T13:14:26Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/218a3b53-095b-4bae-a091-ee26b4b2e2a6.json and https://artists.proofprofile.net/proofs/artist/218a3b53-095b-4bae-a091-ee26b4b2e2a6.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 0x9388f135a4893d11ec68987e4633bb4b98f288ed0d7e206617bcd615f56c69f1. Chain 2 (Bitcoin): anchored in block 960327 (2026-07-31T00:26:26Z), 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/GB8KE2212587.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc66d9b982a536e44756c5d8d455a55338fd5d284a6f5699c72cb9315c6a6de4b. Chain 2 (Bitcoin): anchored in block 957055 (2026-07-07T15:12:44Z), 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/GB8KE2212601.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x67ddc19b4cdbfee252002c181137ea77fe6be382ffff2a5e3c082724e3073fca. Chain 2 (Bitcoin): anchored in block 957118 (2026-07-08T03:20:19Z), 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/GB8KE2212604.