Verify bootcamp certificates on the blockchain

What it means to verify a bootcamp certificate on blockchain

When your bootcamp issues a certificate, the file itself is easy to copy, screenshot, or forge. Anchoring it on-chain fixes that. Your browser computes the certificate's SHA-256 hash — a 64-character fingerprint unique to that exact document — and an issuer signs the register_certificate transaction, binding the hash to the graduate's Stellar wallet.

From that point the credential has an on-chain record: who issued it, which wallet owns it, and its status. Anyone can confirm the proof against the live contract on Stellar testnet without contacting your registrar. Verification stops being a favor your admissions staff does over email and becomes a public, read-only lookup.

• SHA-256 hash binds one exact certificate file to one graduate wallet
• register_certificate writes the record on-chain and emits a cert_reg event
• Credentials move through explicit statuses: issued, verified, suspended, revoked, expired

Tamper-evidence: duplicate hashes are rejected on-chain

The contract will not let the same certificate hash be registered twice. A second attempt to anchor an already-registered hash fails with an AlreadyExists error before anything is written. Nobody — not another issuer, not a bad actor — can quietly overwrite or re-mint a credential your school already anchored.

Because the hash is derived from the document, any edit to the certificate (a changed name, date, or grade) produces a completely different hash that will not match the anchored record. That mismatch is the tamper-evidence: an altered file simply won't verify.

The public proof page your graduates share

Every anchored credential gets a public proof page. A graduate pastes the 64-character hash — or shares the link — and the page shows the on-chain record, the issuing organization's trust status, the credential's current status, and any attached evidence. No wallet, no account, no login is required to open it.

That means an employer in another country can confirm a certificate the moment they receive it, and your graduate controls the link they hand out. A wallet is only ever needed to issue, verify, or pay on-chain — never to read a proof.

• Wallet-free and login-free — verification is public and read-only
• Shows credential status, issuer trust status, and on-chain evidence
• Every action is auditable on stellar.expert via the emitted events

The issuer trust registry

A proof is only as good as the organization behind it, so issuers are first-class, on-chain identities. Your bootcamp self-registers with register_issuer and enters a pending queue; an admin approves it with approve_issuer before it can issue or verify anything. Approved status is visible on every proof page your credentials appear on.

This two-step trust handshake is what lets an employer distinguish a credential from an approved issuer from one issued by an unverified wallet — without you vouching for it manually. An admin can also suspend an issuer, which is reflected on-chain immediately.

Verification and payment, bound in one flow

Most credential tools stop at issuing a badge; background-check firms only do verification. Stellaroid Earn sits at the intersection: once a credential is verified, the same flow can settle payment. An employer calls link_payment, which sends XLM through the native Stellar Asset Contract straight to the graduate's verified wallet — testnet settlement is typically under five seconds and costs a fraction of a cent.

For a bootcamp, that closes the loop between the proof you issue and the outcome your graduates are chasing: verified work that an employer can trust and pay against without an invoice or a middleman.

Why it holds up