Amo or AMO may refer to: Places Amo, Indiana, United States, a town in Hendricks County Amo Creek, a river in Alaska Amu Darya, a river in Central Asia, sometimes referred to as "Amo" Amo Township, C
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 0x48d113911eff718b834f7e900916610ac05f403d1aab3ee0c1826b1fbd0b90d7. Chain 2 (Bitcoin): anchored in block 954342 (2026-06-19T03:22:39Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/830abef7-76cb-4e2e-9a80-d7656fe8c738.json and https://artists.proofprofile.net/proofs/artist/830abef7-76cb-4e2e-9a80-d7656fe8c738.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 0x30c3c1d015d666c4731d658c17c6365ebc88a9e8f9e90d93b958e46ee706336b. Chain 2 (Bitcoin): anchored in block 959109 (2026-07-22T07:21:40Z), 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/QZK6M2518009.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa20084ae9012bc173c6102561c8fb6cdf0fa00c39da0fe0cc41382e7a315f22e. Chain 2 (Bitcoin): anchored in block 958897 (2026-07-20T14:57: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/QT3EZ2549966.