REDIRECT Variants of SARS-CoV-2#Further sublineages emerging in 2024: KP.1.1, KP.2 ("FLiRT"), KP.3 ("FLuQE")
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 0x974ee177eb069e3194275d5803f2a4471df2340d2c039b2b39cdc9ef04c42388. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a1052bae-27cc-4a80-8f73-b1501533ed6d.json and https://artists.proofprofile.net/proofs/artist/a1052bae-27cc-4a80-8f73-b1501533ed6d.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 0x9b0de59569fe2cfb91dccdc9e5bbaf15026d1e93393cbbe608f53262b29f4527. Chain 2 (Bitcoin): anchored in block 958722 (2026-07-19T11:03:50Z), 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/THMUN2310029.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x057afd18888ef8e2a02e8c247f0e530e462ae6f9cda5e2e5c3680d80dac1e279. Chain 2 (Bitcoin): anchored in block 957785 (2026-07-13T01:55:31Z), 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/THMUN2510060.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf51efa9f70db75738af858a25039333d45612573d81788ce41e71609bccaaee0. Chain 2 (Bitcoin): anchored in block 959123 (2026-07-22T11:35:32Z), 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/THMUN2550049.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa5a0aa9a506004236e19b34c5e64fa40261f7785dda79ba7d55b2a6feb92ac6e. Chain 2 (Bitcoin): anchored in block 958538 (2026-07-18T10:30:13Z), 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/THMUN2550050.