Sig used as a name may refer to: Sig (given name) Sig, Algeria, a city on the Sig River Sig Alert, an alert for traffic congestion in California, US Sig, Denmark, a village in West Jutland, Denmark Si
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 0x89bbad74335b10497f98a01dedae43c911535b2495e1b577ab8112ac0d154cbe. Chain 2 (Bitcoin): anchored in block 953654 (2026-06-14T16:26:51Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/4a1c502f-9469-47c6-8f6c-0a3175902c2e.json and https://artists.proofprofile.net/proofs/artist/4a1c502f-9469-47c6-8f6c-0a3175902c2e.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 0x7b0f17388e2887e820ab61fbdc5768f0dbe777e7c7ad1ffaea01a5da4a72c2af. 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/TCJPD2402151.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8d5890610d8d71d43eb89a1696e0e68a2438e45b96422c0c0033a54231b1a627. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12:41Z), 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/TCJPD2428116.
SUSHI SANZAI (feat. Zundamon, KASANE TETO & Chis-A)
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x170c5d9e5260560d7663559492fc61eb5da4499a2c97f6bce566442d54283262. Chain 2 (Bitcoin): anchored in block 956889 (2026-07-06T06:56:49Z), 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/TCJPG2558940.
すしさんざい (feat. ずんだもん, 重音テト & 知声)