Teck may refer to: Teck Castle (Burg Teck) in Württemberg, Germany Teckberg, mountain on which Teck Castle is located Duke of Teck, a title of nobility, associated with Teck Castle Teck Railway,
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 0x4092c25f42e3d9ce7f7c5ce64287eb8c44cdfad7d06b15c8638f488fce7f993a. Chain 2 (Bitcoin): anchored in block 954038 (2026-06-17T02:57:22Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/3e2dc76b-203c-4d95-b45c-d51956e64db1.json and https://artists.proofprofile.net/proofs/artist/3e2dc76b-203c-4d95-b45c-d51956e64db1.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 0x293625eb27ab167307ea8d41d34fc93e7cccb7bfdc777ea36faae07a9ce3d8f3. Chain 2 (Bitcoin): anchored in block 960497 (2026-08-01T02:22:04Z), 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/AUBEC2184907.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x641099f043f28b847bb3a9c6045772ffb62f2cac2b79d28fdae7f8f16dbdf8c9. Chain 2 (Bitcoin): anchored in block 957120 (2026-07-08T03:22: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/AUBEC2167997.