Bino may refer to: Binoculars Bino (footballer, born 1940), Portuguese footballer Bino (footballer, born 1972), Portuguese footballer Bino (particle) Bino (singer) (1953–2010), Italian pop singe
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 0xf68911c03e83e24bf3d25ae0e910ae1bd6ce392e410c6452adfadb25720f3248. Chain 2 (Bitcoin): anchored in block 953717 (2026-06-15T01:05:33Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/894ef286-59d7-4727-a690-4f8b877dbab3.json and https://artists.proofprofile.net/proofs/artist/894ef286-59d7-4727-a690-4f8b877dbab3.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 0x19542175115872a8730599b5a040780e8b224610ed22a908f722fa5c8dad12c3. Chain 2 (Bitcoin): anchored in block 958547 (2026-07-18T12:44:05Z), 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/FR9W12451207.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xd98eb74f46b4f7519b73d5820cbf28e2156c11c73215ab6bb20ec3e43cf144cd. Chain 2 (Bitcoin): anchored in block 958935 (2026-07-20T22:08: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/FR9W12451208.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9dee4ca5b113932595f8656a22f681f21d5bfe279d274f2d6eb2a6a942b16f02. Chain 2 (Bitcoin): anchored in block 956772 (2026-07-05T10:01:46Z), 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/FR9W12546841.