Move batch work out of the request
Credential batches can take longer than a single web request. A queue with retries and backoff keeps issuance work separate from the interactive setup flow.
Loading
Digital credential platform
CredKit is a credential-authoring and issuance product I am co-building. The prototype covers the path from designing a credential and preparing recipients to issuing credentials and letting a recipient check their authenticity.
(01) The problem
Issuers need to create credentials in batches and give recipients a way to verify them later.
(02) What I worked on
Built a canvas-based editor for arranging variable credential templates and previewing recipient-specific output.
Implemented recipient import, preview, issuance steps, status handling, and asynchronous jobs for batch work.
Implemented SHA-256 hashing, Ed25519 signing, and Merkle proof helpers used by the credential verification flow.
Personally reviewed the application and made targeted remediations in the areas examined; this is not an external certification of the whole product.
(03) Engineering decisions
Credential batches can take longer than a single web request. A queue with retries and backoff keeps issuance work separate from the interactive setup flow.
The prototype exposes hashes, signatures, and batch proof helpers so a verifier can check a credential against the data represented by the issuance process.
(04) Delivery & status
A working credential lifecycle prototype. It is not presented as a production launch or independent security certification.
(05) Technology