Pullman may refer to: Places in the United States Pullman, Chicago, Illinois Pullman, Michigan Pullman, Texas Pullman, Washington Pullman, West Virginia Pullman Lake, a lake in Minnesota Pullman neig
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 0xdf1e4cc652f38c47adab4aae2b7c40bbe8f676c744536f247e7272a9c7d56cee. 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/ed04fd62-33fe-4c98-bf98-ae05e4a68d22.json and https://artists.proofprofile.net/proofs/artist/ed04fd62-33fe-4c98-bf98-ae05e4a68d22.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 0x79c263161e9fe0a6f88e083dd61b60537c7d37df75bb36aefc0d7094b75786c7. Chain 2 (Bitcoin): anchored in block 958166 (2026-07-15T15:55:19Z), 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/USTJ20305501.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xeb578ad11050fd067fd9f025f948256e3978296352f7afee07744edd009c7f00. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), 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/USTJ20305503.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x741d2d6e4f1657b4afa73e6ca7b9004fe777781592fbd4583b2f586c02ffd370. Chain 2 (Bitcoin): anchored in block 959118 (2026-07-22T10:01:58Z), 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/USTJ20305507.