Benner may refer to: Benner (surname) Benner Township, Pennsylvania Benner, United States Virgin Islands USS Benner, the name of more than one United States Navy ship
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 0xe616e63f5b03563acc63cc9ffc72c8f5c65de85ffb545e2cce6e774afe5973d6. 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/5a6a2c42-68b6-4a3f-990c-3787c39ef93c.json and https://artists.proofprofile.net/proofs/artist/5a6a2c42-68b6-4a3f-990c-3787c39ef93c.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
FSOE 801 - Future Sound Of Egypt Episode 801
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 0x38b806d5735b70f5abb92e08bf8dff5a6630a3bb1c7ad72e726fb13e80423adc. Chain 2 (Bitcoin): anchored in block 960468 (2026-07-31T21:25:57Z), 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/UKRMQ2300412.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf329e587eb214e99a598d9d4324e6e41a1fb731c1626029fb06b145fdc2cc3f5. Chain 2 (Bitcoin): anchored in block 960191 (2026-07-30T01:51:26Z), 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/GBVVQ2301007.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x178c0bc7ae3bce28318d8736ab7f6ab28052d6de17afb8606d8b625dc0ae8bbb. Chain 2 (Bitcoin): anchored in block 957118 (2026-07-08T03:20:19Z), 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/GBVVQ2301008.