Tomio is a masculine Japanese given name. Written forms Tomio can be written using different combinations of Kanji characters. Some examples: 富雄, "enrich, masculine" 富男, "enrich, man" 富夫, "enrich
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 0xca0d98aefdd98a243781232043dcc25fe27e003aad71c62981560ed5f6d1d258. Chain 2 (Bitcoin): anchored in block 953915 (2026-06-16T08:36:32Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/1acae876-3e4e-40e6-9afb-04ec55907f50.json and https://artists.proofprofile.net/proofs/artist/1acae876-3e4e-40e6-9afb-04ec55907f50.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 0x40d2028914891e2abe29f6e51c8b87855f039972b19f8da368466ab941a02776. Chain 2 (Bitcoin): anchored in block 958444 (2026-07-17T19:12:23Z), 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/QZRP42461205.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0b7729f1d49ce707eb868bb467b1fa2233f8742e4f4b111b93fdd23f8040466b. Chain 2 (Bitcoin): anchored in block 958913 (2026-07-20T16:58:47Z), 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/QZZ7L2473439.