Gemma or GEMMA may refer to: People and fictional characters Gemma (given name), including a list of people and fictional characters with the name Gemma (surname), including a list of people with t
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 0x8fe4dc4820ca28453b888275648455ee32d9401298cfddd1c7e7aac9263f5ba3. Chain 2 (Bitcoin): anchored in block 953697 (2026-06-14T21:49:28Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/5d979884-dd6a-449f-8bda-b6a428eb37cd.json and https://artists.proofprofile.net/proofs/artist/5d979884-dd6a-449f-8bda-b6a428eb37cd.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 0xbcced05accb585af9f1f174dca8348807d8ad6124b32b4b2f18cd8944c4f3461. Chain 2 (Bitcoin): anchored in block 956578 (2026-07-04T02:23:20Z), 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/QZK6M2011870.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x02c06a23359d276b84d471c26ac9ad9d141af10c43cdc6373150db13410d380d. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), 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/QZFZ22437526.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3aa7359ba126ff8319b9cd4ebeb22b225d7d0ea0fcbf4cf5f666ff119ee19f44. Chain 2 (Bitcoin): anchored in block 958955 (2026-07-21T03:03:40Z), 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/QZPLR2298747.