Tomer may refer to: Tomer (name), a Hebrew given name Tomer (Israeli settlement) See also Tomar (surname) Tomor (disambiguation)
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 0x5d06b933da9bce747b51de5690b370f232aac12c5e8beace9b61e5672b0cd5a5. Chain 2 (Bitcoin): anchored in block 953762 (2026-06-15T08:21:23Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/b8fa6c8a-973c-45ef-8960-0de49b8ddcea.json and https://artists.proofprofile.net/proofs/artist/b8fa6c8a-973c-45ef-8960-0de49b8ddcea.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 0xd22fca0fa5957aedca5e953a3b7e2910d077b2c31410eb003c51b076e8472adc. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48: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/QZ8251801416.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x040be863814a0863067452c8ee102e2b1ce55adbb198f98dbac212a63f33f2d1. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/QZ8251815731.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x5eb7a4766e0b99ed0f39b79d225e015930c5007cac3520a71c2ee0966fab320b. Chain 2 (Bitcoin): anchored in block 958444 (2026-07-17T19:12:23Z), 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/USCGH1937715.