Majki may refer to the following places: Majki, Ostrołęka County in Masovian Voivodeship (east-central Poland) Majki, Sierpc County in Masovian Voivodeship (east-central Poland) Majki, Warmian-Masuria
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 0x19062dc00d752df802e683b34aee7388ed4ae31f271eeca474e8d956cfb5225c. Chain 2 (Bitcoin): anchored in block 953727 (2026-06-15T02:33:01Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/9193ee4e-614b-4da7-a049-eeb16937d285.json and https://artists.proofprofile.net/proofs/artist/9193ee4e-614b-4da7-a049-eeb16937d285.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 0x1e222c9ceea3bfe30b004038bcfa31942c60925f0a3d6ce3060c3c5f4348a06d. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48:28Z), 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/QZNWZ2095827.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe8de846282cde982d80e9532beda28a790e97ecbb83797ba3122f31e54da00a0. Chain 2 (Bitcoin): anchored in block 957891 (2026-07-13T18:21:04Z), 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/QZFYY2101329.