Doichain Seal

Doichain Seal

A free, tamper-evident timestamp for every software release. No account, no wallet, no secrets.

The Doichain Seal GitHub Action computes the SHA-256 of your release files and anchors it in the Doichain blockchain. The job proves its identity with a GitHub OIDC token, so the seal carries repository, tag and commit. Anyone can later check that a download is exactly the file you published, and since when it exists.

Seals
80
Repositories
35
Today (UTC)
0

Add it to a release workflow

permissions:
  contents: read
  id-token: write   # lets the job prove its identity to the seal service

steps:
  - uses: actions/checkout@v4
  - run: ./build.sh            # produces dist/*
  - uses: neubuot/doichain-seal@v1
    with:
      files: dist/*

Then put the seal into your README (the large seal, or the compact badge with badge.svg):

Doichain seal Doichain seal badge

[![Doichain Seal](https://doi-api.sendlabs.de/seal/github/OWNER/REPO/seal.svg)](https://doi-api.sendlabs.de/seal/github/OWNER/REPO)

What the seal proves

Limits: 20 seals per repository and day, 300 per day for everyone. Names expire after 36,000 blocks (about 250 days), the timestamp stays in the chain history forever. Repository, tag, commit and file name are public on the chain.

Latest seals

RepositoryReleaseWhen
neubuot/kerbholzv0.2.02026-10-14 17:48:22 UTC
neubuot/kerbholzv0.2.02026-10-14 17:48:21 UTC
neubuot/kerbholzv0.1.02026-10-14 10:32:51 UTC
neubuot/kerbholzv0.1.02026-10-14 10:32:50 UTC
neubuot/urschriftv0.2.02026-10-14 08:54:58 UTC
neubuot/urschriftv0.2.02026-10-14 08:54:57 UTC
neubuot/urschriftv0.1.02026-10-14 08:11:17 UTC
neubuot/urschriftv0.1.02026-10-14 08:11:16 UTC
neubuot/Werbeeinwilligungmain2026-10-14 02:30:25 UTC
neubuot/talent-academy-vorschaumain2026-10-13 22:35:37 UTC