Moe, MOE, MoE or m.o.e. may refer to: In arts and entertainment Fictional characters Moe, leader of The Three Stooges, played by Moe Howard Moe Szyslak, from the animated television show The Simpso
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 0x0c958718aaf93cac49e745b490144ba11d9e5bca3f1336494568de378b033e5b. Chain 2 (Bitcoin): anchored in block 953907 (2026-06-16T07:39:24Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/160ca10a-2d6f-4fc6-bf90-4788bac7c58d.json and https://artists.proofprofile.net/proofs/artist/160ca10a-2d6f-4fc6-bf90-4788bac7c58d.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 0xae0b1f0afa39f1e81d02638a7065ca98a4bef9d92d3200863da245bc081b9727. Chain 2 (Bitcoin): anchored in block 956551 (2026-07-03T21:18: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/MMA031912610.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb5c1285b203edffa2bf1e5abcd53870e3f5b41158aee601c3fbe70a75b80e41b. Chain 2 (Bitcoin): anchored in block 958436 (2026-07-17T16:42:22Z), 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/MMA031915336.