Hypercerts

Services

The work a product alone does not finish.

Connecting to the systems you already run, meeting the regulation that applies to you, getting through the test suites. It is also the work that produced Veritra.


01

DID / VC · eIDAS 2.0 system builds

We build the capability for an institution to issue and verify credentials itself, from the ground up. The standards choices — SD-JWT VC or mdoc, which DID method — are decided with you rather than handed to you.

Included
Requirements · trust model design · schema definition · installation and core-system integration · handover
Deliverables
Requirements specification · architecture document · operations guide
02

Wallet · relying party integration

Verification added to a service that already exists. OID4VP presentation verification goes into your sign-in or identity-check flow, and we build the endpoint that accepts requests coming from a wallet.

Included
Presentation request design (DCQL) · verification endpoint · integration with the existing authentication flow · interoperability testing
Deliverables
Integration specification · verification flow document · interoperability test results
03

Conformance · certification support

We help an implementation get through the OpenID Foundation conformance suites. The traps we hit taking 62 issuer, 10 verifier and 12 wallet modules through ourselves are what you are buying.

Included
Assessment of the current implementation · suite environment setup · per-module failure analysis and remediation · re-runs
Deliverables
Assessment report · conformance execution results · remediation guide
04

Blockchain · Web3 engineering

On-chain work in an identity context: an agent identifier held on-chain and bound to a verified operator identity, or entitlement to a tokenised asset expressed as a credential. We design and implement both.

Included
Contract design and implementation · on-chain identity registry · credential binding design
Deliverables
Contract specification · deployment configuration · integration design

How an engagement runs

  1. 01

    Kick-off

    Goals and constraints first. What we will not build gets settled before what we will.

  2. 02

    Requirements

    Credential schemas, trust model, systems to integrate with. Written down.

  3. 03

    Design · build

    Progress shared weekly.

  4. 04

    Verification

    Conformance suite and integration testing. Results are submitted as they come out.

  5. 05

    Handover

    Operator training and incident procedures included.

Contract form

Fixed scope — priced against deliverables

Working mode

Remote-first · kick-off and handover on site

Maintenance

Annual option · includes standards revisions

Tell us what the work is.

An undefined scope is fine at this stage. We start by agreeing what not to build.