Verification chip — bRRAIn Docs

What a chip is, how to issue one, and how recipients verify it.

Verification chip

A verification chip is a short-lived, signed token tied to your bRRAInUserID that you can attach to anything (resume, contract, code commit, design file, blog post). When a recipient checks the chip, they confirm:

  • The artifact came from you.
  • Your ID was active at issuance.
  • The credentials you claimed (e.g., a certification) were valid at issuance.

When you'd issue one

  • Resume — prove every credential listed is real and verified.
  • Contract — prove the signing party's identity.
  • Code commit — prove authorship for code that needs provenance.
  • Design file — prove authorship for IP-protected work.
  • Blog post / article — prove the byline is real.
  • Auditor report — a CPA or auditor signs their findings.
  • Any artifact whose provenance matters.

Issue a chip

From your profile (signed in) → Issue chip:

  1. Pick a scope — what the chip identifies. Common scopes: resume, contract, code-commit, general.
  2. Pick expiry — chips are short-lived by design. Defaults: 90 days for resume, 30 days for contract, custom for general.
  3. Optionally add scope data — extra context (e.g., for a contract chip, the contract's title and counterparty).
  4. Click Issue. We generate the chip immediately.

You're given:

  • A verify URL — https://id.brrain.io/verify/chp_8a2b3c.... Recipients click to verify.
  • A QR code — embed in physical artifacts.
  • An HTML embed — drop into web pages.
  • A Markdown embed — drop into markdown documents (GitHub READMEs, etc.).

How verification works

Anyone (no bRRAIn account required) can hit the verify URL. They see:

  • Your display name and avatar.
  • The certifications you opted to surface in this scope.
  • The issuance and expiry timestamps.
  • A green / amber / red verification status.

Status:

  • Green — chip is valid, current, and ID is active.
  • Amber — chip is expired but was valid at issuance.
  • Red — chip is invalid, revoked, or never existed.

Revoking a chip

If a chip's been compromised (the artifact it was attached to was stolen, lost, or repurposed), revoke it:

  • From your profile → Issued chips → row action → Revoke.
  • Revocation is immediate.
  • Verification of a revoked chip shows red with the revocation reason.

You can also revoke all chips with a single Sovereign action — useful in account-compromise scenarios.

What recipients see vs what stays private

The verify page shows what you opted to surface for the chip's scope. Things never shown publicly:

  • Your account email.
  • Your password / MFA state.
  • Your organization memberships beyond what you opted to surface.
  • Your other chips.
  • Your private profile fields.

Free vs Pro

  • Free — issue up to 5 active chips at a time; expiry capped at 90 days; standard verify-page styling.
  • Pro — unlimited chips; custom expiry up to 5 years; branded verify page with your logo and palette; chip analytics (verify counts, geographic distribution); custom scopes.

API

Programmatic chip issuance via API: Registry. Useful for automating chip embedding in your CI/CD pipeline (e.g., automatically chip every signed release commit).

Where to next