Verification & infrastructure

Traditional credential systems rely on a central database or the issuer to confirm authenticity. That means slow verification, single points of failure, and credentials that don't travel across borders. Blockchain solves three problems at once.

• Immutability — Once a credential is recorded on-chain, it cannot be altered or deleted by anyone: not the provider, not thriveDispatch, not the regulator. The record is permanent.
• Decentralised verification — Anyone can verify a credential by querying the blockchain. No need to trust our servers, call the provider, or contact the regulatory body. The chain is the source of truth.
• Portability — A credential on a public blockchain is valid wherever the chain is accessible. Cross-border recognition becomes automatic.

Recording a certificate on Ethereum mainnet at peak gas prices can cost tens of dollars per transaction — more than the certificate itself in many markets. That makes blockchain credentialing financially unviable in price-sensitive regions.

Arbitrum is an Ethereum Layer 2 rollup: it compresses transaction costs by over 90% while inheriting Ethereum's security. Gas fees on Arbitrum are typically under one cent per transaction. For a platform issuing tens of thousands of credentials a year, that difference is the difference between a viable product and an academic exercise. Arbitrum also gives sub-second finality, so a hiring manager scanning a QR code gets verified confirmation immediately.

thriveDispatch deploys three focused smart contracts on Arbitrum.

• Provider registry — Maintains the on-chain list of authorised CPD providers. Only addresses controlled by verified regulatory bodies can add or remove providers. This is the source of truth for who is allowed to issue credentials.
• Credential issuance — Records each certificate on-chain. It accepts batches of credential hashes (e.g. merkle root), verifies the caller is a registered provider, and emits events. Individual certificates are verifiable via merkle proof without storing each one as a separate transaction.
• Verification — Enables third-party verification. Input a credential ID; the contract returns validity, issuance metadata, and blockchain proof. No thriveDispatch server has to be running for the query to work.

Healthcare credentials involve personal data. We use a hybrid design: sensitive information (name, licence number) stays in an encrypted off-chain database. Only cryptographic hashes and non-personally-identifiable metadata are written on-chain.

A third party verifying a credential learns that a valid credential with specific attributes exists — they do not see the underlying personal data unless the professional explicitly shares it. This satisfies data-protection requirements while keeping blockchain's verification benefits.

Instead of one blockchain transaction per certificate, thriveDispatch batches certificates issued in a time window into a single on-chain transaction using a merkle tree. Each certificate still has an individual proof that can be extracted from the tree, so verification remains per-credential.

As volume grows, per-credential cost drops. Unit economics improve with scale — the more the platform is used, the cheaper it becomes to operate.