Berek may refer to: Places Berek, Croatia, a municipality Berek (Gradiška), village in Republika Srpska, Bosnia and Herzegovina People In Polish, Berek is a diminutive of the names Baruch or Ber
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 0x1f5fce8c242bbf569e6e3a9e86de7df8e1359f3ed1b56ccdfe934c862ed41188. Chain 2 (Bitcoin): anchored in block 954066 (2026-06-17T08:11:48Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/7621b847-f0eb-47b9-971a-bb8b918aa83f.json and https://artists.proofprofile.net/proofs/artist/7621b847-f0eb-47b9-971a-bb8b918aa83f.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 0xbf7a3b62a451460531b9e89f60b2ff6f30279661f03f4c82c0d94366df4ca0d1. Chain 2 (Bitcoin): anchored in block 958838 (2026-07-20T07:01:21Z), 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/GXBAV2010588.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xaded0381deaafb9766890e29ee966328e7e7e2bca193b74dad8672b6548cbb9f. Chain 2 (Bitcoin): anchored in block 958903 (2026-07-20T15:22:45Z), 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/QT5M32557035.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xfd3d3d8285a836444b4616612d772a1d45bb9d8c173b0bdb185afce15ae219c4. Chain 2 (Bitcoin): anchored in block 959144 (2026-07-22T15:38:35Z), 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/QT5M32552667.