Nango may refer to: Places in Japan Nangō, Aomori, a former village in Aomori Prefecture Nangō, Fukushima, a former village in Fukushima Prefecture Nangō, Miyagi, a former town in Miyagi Prefecture
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 0xaa9ec2ba3e27a581e0963c1f364d1e100b47f5fcfb68010a6da4d609fbef2180. Chain 2 (Bitcoin): anchored in block 953721 (2026-06-15T01:12:01Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/8ae3ff4a-2402-4370-8380-330c2c7a3b46.json and https://artists.proofprofile.net/proofs/artist/8ae3ff4a-2402-4370-8380-330c2c7a3b46.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 0x05470361542a70e9252d38ef9fd5ce5ba9758cdc536cea6f4ba2939e3cd75f30. Chain 2 (Bitcoin): anchored in block 958276 (2026-07-16T10:20:17Z), 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/ESA092414761.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb02137182b20f36eed1c3839fa43c24d68a9a93b5f36832318c67c88c9e59ad0. Chain 2 (Bitcoin): anchored in block 958286 (2026-07-16T12:43:37Z), 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/ESA092501850.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xfd8e742f4d170a09835d22b2f7fcb49a8b809fef2aae96032f939cbb38fa046e. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/ESA092503219.