Chane may refer to: Chané, an indigenous people of South America Chané language, an extinct Amerindian Chañe, a municipality in Spain Chane, Bhiwandi, a village in Bhiwandi taluka, India Chane (
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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0ca2f0dfbefa38859b8afe99e51f41c1bd2582f975cbdc4fd1542ca1fe1f4a8e. Chain 2 (Bitcoin): anchored in block 953773 (2026-06-15T10:40:45Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/c552e7a1-376a-4d98-a983-3c5ab8d81bf4.json and https://artists.proofprofile.net/proofs/artist/c552e7a1-376a-4d98-a983-3c5ab8d81bf4.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Reggaetón Cumbiatón Perreo (feat. Cris Sour, Alu Mix)
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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x14732af61cfdf148d39c0232bcecd91abbb6d0412ef30eeb5eb38e1059c80f6e. Chain 2 (Bitcoin): anchored in block 953536 (2026-06-13T17:25:41Z), 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/ZZOPM2221726.
Bienvenida (feat. CHANE, Jencko el Shinobi,Cris Sour, Alu Mix) - Remix
Bienvenida (feat. CHANE, Jencko el Shinobi,Cris Sour, Alu Mix) [Remix]
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xac14d76c5ad2e8c9ea0a4035107b20892220f4aa5e08acaf66d30f0169d848d6. Chain 2 (Bitcoin): anchored in block 960108 (2026-07-29T13:09:35Z), 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/ZZOPM2115521.
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