John Neville may refer to: John Neville, 3rd Baron Neville (c. 1330–1388), English nobleman and soldier John Neville, Baron Neville (c. 1410–1461), English Lancastrian nobleman and soldier John Nevil
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 0xfd03aaf132700f2e6c2ba554f93fed34ee5fd0251d0073cde99569b6299c4d9a. Chain 2 (Bitcoin): anchored in block 953817 (2026-06-15T18:10:31Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/fc362643-0080-4a37-8cee-b3856e34e122.json and https://artists.proofprofile.net/proofs/artist/fc362643-0080-4a37-8cee-b3856e34e122.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Bird Songs of the Central Boreal Forest Ontario and Manitoba including Churchill
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 0x739612ba6551c06e59e85173468699ed76eced9440b346e98f2e2209e74cdff5. Chain 2 (Bitcoin): anchored in block 958924 (2026-07-20T21:48:48Z), 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/CAM021420087.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9d6b0d10fbdcdd2b8cbba09b284bfce5ae86e4b3e04f67655dfaac4ff8486eab. Chain 2 (Bitcoin): anchored in block 956634 (2026-07-04T10:04:33Z), 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/CAM021420088.