Migo may refer to: People Hisao Migo (1900–1985), Japanese botanist Migo Adecer (born 1999), Filipino-Australian singer Other uses Mi-Go, a fictional race of extraterrestrials created by H. P. Lovec
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 0x9e9ac87b430962df2fb4f0a4b61ba6d6e40443ca2f945cbed4ba80bc3e3bad3c. Chain 2 (Bitcoin): anchored in block 953803 (2026-06-15T15:41:00Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/e9724174-5593-46db-9bba-3a46beb67fcc.json and https://artists.proofprofile.net/proofs/artist/e9724174-5593-46db-9bba-3a46beb67fcc.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 0xdeae389d20d4f9e26aa8b9710e0a75c7b79931c9ac91a62608cbe48ddddf5765. Chain 2 (Bitcoin): anchored in block 960144 (2026-07-29T21:09:47Z), 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/DEP551000692.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x47483af42f382ae63b8f25ae4f8a37c668c821da13be1d5cd3c4ffb6767e1f0b. Chain 2 (Bitcoin): anchored in block 953513 (2026-06-13T12:47:07Z), 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/DEN061501477.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x47483af42f382ae63b8f25ae4f8a37c668c821da13be1d5cd3c4ffb6767e1f0b. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/DEN061501477.