Intribe turns academic results, health records, certifications, and achievements into cryptographically signed, blockchain-verified credentials that recipients own, control, and share on their terms.
No credit card required · W3C open standards · Export any time
University of Edinburgh
Result
Distinction
Issued
15 Jun 2025
Built for any
verifiable claim
For issuers
Whether you run enterprise software or a weekend workshop, Intribe meets you where you are.
Connect your campus ERP, hospital information system, event management platform, or any data source via the Intribe API. Records, results, and reports are automatically signed and issued as verifiable credentials in bulk — no workflow changes required.
Running a marathon, summer camp, clinic, workshop, or certification program? No system needed. Upload a spreadsheet — CSV or Excel — through our portal. We sign, batch, anchor, and issue credentials to every recipient in one go.
Either way, every credential gets the same cryptographic guarantees: signed, batched, and permanently anchored on the blockchain.
For recipients
Three steps. Full control. No intermediaries.
Credentials appear in your personal timeline, cryptographically signed by the issuer — your school, doctor, employer, event organizer, or certification body.
Choose exactly which fields to share. Prove your grade is above 70 without revealing the exact score. Prove you're vaccinated without revealing your full medical history.
Send a QR code or a link. Anyone — an employer, a university admissions office, a hospital — can verify independently on the blockchain. No Intribe account required to verify.
You can also add your own credentials — online courses, self-taught skills, peer endorsements — with transparent trust markers that show exactly how each one was verified.
Trust infrastructure
Every credential runs through every layer on every verification. No shortcuts. No trusted intermediaries.
Cryptographic signature
ES256 signature by the issuer's key. Mathematically proves the credential is authentic and has not been altered.
Issuer verification
The issuer's public key is published in Intribe's transparent registry. Anyone can verify the signature independently — no trust in Intribe required.
Merkle batch inclusion
Credentials are batched daily into a Merkle tree. Membership is provable with a short, auditable proof — without exposing other credentials in the batch.
Blockchain anchor
The batch root hash is published to Polygon Amoy — a permanent, tamper-evident public record that exists independently of Intribe.
Authorized submitter
Only Intribe-approved wallet addresses can publish batch roots. Every submission is traceable on-chain.
Root integrity
The on-chain Merkle root is compared to the database root on every verification request. Any discrepancy surfaces immediately.
Revocation status
A live W3C BitString Status List lets issuers revoke credentials with structured reason codes. Checked in real time on every verification.
For issuers
The same cryptographic infrastructure that powers enterprise credential issuance — available to any organization, any size.
Two integration paths
REST API for organizations with existing systems. File upload portal for everyone else. Same cryptographic guarantees either way.
Bulk or individual issuance
Issue one credential to a single patient or ten thousand certificates to a graduating class — handled in a single batch operation.
Revocation control
Revoke any credential at any time with structured reason codes — issued in error, superseded, suspected fraud. Recipients and verifiers see the status in real time.
Recipients own it
Credentials belong to the recipient, not the issuer. They remain valid even if the recipient leaves your organization, platform, or country.
Ready to issue your first credential?
We can have your first batch live within a day.