The analysis document
A certificate should identify the compound, lot, test methods, result, and date. Compare the document with the public record before relying on a seal.
The verification roadmap · No on-chain issuance claimed
CertikLabs is designing a chain from the product and its lot to the analysis document and public verification page. A unique, independently checkable blockchain link for each test is the proposed next layer; the current anchor previews are illustrative and are not live transactions.
Browse reference recordsA certificate should identify the compound, lot, test methods, result, and date. Compare the document with the public record before relying on a seal.
A QR on a certificate, vial, or carton should resolve to the same public verification ID. The page can show the latest visibility and status for that lot.
SHA-256 must be computed from the exact PDF bytes, not from a record ID. Changing the PDF changes its digest. Current demonstration values are not report fingerprints.
A genuine on-chain proof requires a confirmed transaction and chain explorer link for that fingerprint. Until then, there is no independently checkable blockchain receipt to cite.
Packaging and seal mockups are design concepts, not testing evidence. No invented transaction hash, block number, issuer key, or simulated signature should be used as a certificate of authenticity.
No. The current anchor previews are deterministic examples derived from verification IDs, not blockchain transactions. An actual anchor would need a real chain, transaction hash, block timestamp, and explorer link for the specific report.
It should open the public verification page for that specific lot, where the buyer can compare the product and batch identifier with the document and check the published status. A QR code is a link, not independent proof by itself.
A signed report could be hashed and its fingerprint included in a confirmed public transaction. The verification page would link to the chain explorer, allowing an independent check of the transaction and the exact report bytes. This is a planned capability, not a currently issued proof.
No. Preview values are derived from the verification ID, not from the PDF bytes. Do not interpret them as a SHA-256 checksum of a downloaded report or as evidence of publication on a blockchain.
Related
/about
CertikLabs is a founder-led independent peptide analytical lab in pre-launch. Accreditation in progress — target 2027.
/api
REST endpoints, webhooks, and SDKs for partners integrating CertikLabs verification into their systems.
/ask
Ask questions about CertikLabs' peptide testing, verification reports, pricing, and mail-in submission. Answers are drawn from our public pages and link to the Testing FAQ, lab directory, and cost guides.