Beez may refer to: Béez, a tributary of the Gave de Pau, in Béarn, France Beez, Namur, a sub-municipality of the city of Namur, Belgium Richard Beez (1827–1902), German mathematician "Beez", a so
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 0xd7264571a9346296b5fa4e1d54f56d6036db5acf36557d2ee0efe6e2bae41087. Chain 2 (Bitcoin): anchored in block 954650 (2026-06-21T04:51:12Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/d9b7f3f7-c437-4905-8d3b-765af2e7c9a2.json and https://artists.proofprofile.net/proofs/artist/d9b7f3f7-c437-4905-8d3b-765af2e7c9a2.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 0xd07029f85c9f1f7620669b9278ebdbaa18297d4b65eeaf83affb8529ae589a4e. Chain 2 (Bitcoin): anchored in block 958639 (2026-07-19T01:18:30Z), 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/QZHN71948585.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x12464dfe5abd4c186ab8b1902165919b2e06b812938ed567cf4e0b8841bba466. Chain 2 (Bitcoin): anchored in block 959087 (2026-07-22T02:05:55Z), 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/QZES72016664.