Phoebe or Phœbe may refer to: __NOTOC__ People and fictional characters Phoebe (given name), a list of people, mythological, biblical and fictional characters Phoebe (mythology), several Greek mythol
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 0x945286894400b1ea570176551380f238e84f96e30d1e27a19c7b938e4f6f3300. Chain 2 (Bitcoin): anchored in block 954667 (2026-06-21T07:29:20Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/b1f4a949-96f0-4dac-b304-a1fbd45c752b.json and https://artists.proofprofile.net/proofs/artist/b1f4a949-96f0-4dac-b304-a1fbd45c752b.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Nic nie widzę, nic nie słyszę, nic nie mówię EP
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 0x5007683be7181ec0b7f3ea673215dfe328d544a379c17dfeeaef2a2a16171bea. Chain 2 (Bitcoin): anchored in block 958543 (2026-07-18T11:58:44Z), 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/TCADF1700395.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x814967235d018c166eaa63819f37ed3ed8b4604a69d20bdfcdd63a9b9d5e1767. Chain 2 (Bitcoin): anchored in block 956302 (2026-07-02T03:30:09Z), 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/GBBKS0300106.