Public trust material

AttestLayer Public Registry

AttestLayer Public Registry exposes historical public trust material for inspection. Current decision: PUBLIC-SURFACE LIMITED GO / CUSTOMER-PROCESSING NO-GO. New Registry-dependent issuance and checkpoint-continuity claims are unavailable.

Historical records may contain checkpoint material and timestamps; their presence is not current continuity verification.
The registry is read-only and unauthenticated.
Anyone can inspect published material without treating inspection as continuity verification.

Not technical? Start with Verify instead.

Why a non-technical reviewer might open this page

Confirm that AttestLayer exposes public verification materials
Determine whether a particular workflow is recorded in the public log or uses issuer-key verification only
Inspect keys, checkpoints, and transparency materials if needed

Reviewing a kit?

Use Verify if you already have a kit.zip. Most reviewers do not need raw registry endpoints.

Doing trust review?

Use this Registry to inspect JWKS, checkpoint bytes, entries, and explicit status. Current checkpoint continuity is not claimed.

Proof generation status

Public inclusion and consistency generators fail closed with 501 until independent RFC 6962 conformance vectors pass.

Current trust model

Registry surfacePublicly readable; /ready reports service readiness but is not checkpoint-continuity proof.

Checkpoint statusSelf-issued; current continuity verification unavailable

Checkpoint keyregistry.jwks.json

Receipt keyissuer.jwks.json

External witnessingNot active

External anchoringNot active

Buyer Review Pack inclusionNot active; BRP receipts use the issuer JWKS and do not imply Registry inclusion

Common Actions

Inspect an eligible package: verify.attestlayer.com — browser-local integrity checks for static synthetic or separately evidenced historical material; no current production issuance or Registry continuity is implied
Fetch JWKS: /v1/jwks/registry.jwks.json — advertised key material; current checkpoint-signature and continuity verification are unavailable
Latest checkpoint: /v1/checkpoints/latest.json — latest published checkpoint object, not continuity verification
Proof generators: inclusion and consistency routes currently return 501 pending independent RFC 6962 conformance

Registry Monitor

Latest checkpoint: TpJM49kkWkpK… Tree size: 51 Last append: 2026-05-19T16:17:27Z Root hash: Git_PxjzWfhm… Signer kid: 816ad5318642ff0a

Sample entry

This historical/schema-only example illustrates an entry shape; it is not a current production record or issuance promise:

{
    "leaf_hash": "29ee4e6724d2fceb8b3096f0d1f2fc8133f64f3f96b09c9a1d113794e8b31e55",
  "receipt_id": "samplekit00000001",
    "manifest_sha256": "41305f4c552d5e56fe5135ad9e321873fe2faa058efd8c28fbf8e018263a64de",
  "issued_at": "2026-06-01T00:00:00Z",
    "receipt_kid": "8adefa300a1059bc"
}

This is a historical/schema example only.
It does not prove a current key, signature, checkpoint, inclusion path, or continuity chain.
New Registry issuance and customer processing remain unavailable under the current decision.

# Fetch latest published checkpoint object (not continuity verification)
curl -s https://registry.attestlayer.com/v1/checkpoints/latest.json | python3 -m json.tool

# Request the fail-closed checkpoint-continuity status
curl -s https://registry.attestlayer.com/v1/checkpoints/chain-verify | python3 -m json.tool

# Inspect the signed historical migration boundary
curl -s https://registry.attestlayer.com/v1/migrations/current.json | python3 -m json.tool

Core Log

GET /v1/entries/{leaf_hash}.jsonLeaf record by hash; substitute an exact 64-character leaf hash

GET /v1/statsRegistry statistics (tree size, dates, checkpoint)

GET /v1/integrityLeafStore integrity report (rolling digest, reconciliation)

GET /v1/snapshotSigned snapshot of checkpointed state (for archival/diligence)

GET /v1/logs/datesAvailable log dates

GET /v1/logs/{date}.ndjsonDaily append log (NDJSON)

Proof generators (fail closed)

GET /v1/proofs/inclusion?leaf_hash=XReturns 501 pending independent RFC 6962 conformance vectors

GET /v1/proofs/consistency?from_size=A&to_size=BReturns 501; the legacy generator is not relied upon

Checkpoints

GET /v1/checkpoints/latest.jsonLatest published checkpoint object; signature/continuity verification unavailable

GET /v1/checkpointsList recent checkpoints

GET /v1/checkpoints/{hash}.jsonSpecific checkpoint by hash

GET /v1/checkpoints/history.jsonlNewest-first cursor-paginated linked suffix (JSONL); follow the Link header to the signed migration boundary

GET /v1/checkpoints/chain-verifyFails closed with verification_unavailable until continuity is independently release-proven

GET /v1/migrations/current.jsonInspect the published historical migration-boundary record without inferring continuity

Witnesses (self-issued; no external witness)

GET /v1/checkpoints/{hash}.witnesses.jsonWitness cosignatures for a checkpoint

Anchors (not yet active)

GET /v1/anchors/External timestamp anchors

Keys / Spec / Tools

GET /v1/jwks/registry.jwks.jsonAdvertised Registry key set; current checkpoint-signature/continuity verification unavailable

GET /v1/jwks/issuer.jwks.jsonIssuer receipt-signing public keys

GET /v1/verify-kit.zipRetired (501); use the complete package and its instructions with the hosted verifier

GET /v1/specRegistry specification & constants

GET /v1/spec/REG-1.0.mdREG-1.0 specification document

GET /v1/verify/chain/{date}Legacy endpoint retired (501)

REG-1.0 · SHA-256 + Ed25519 · RFC 8785 JCS · public proof generation disabled pending conformance