Skip to content

x/cert — Certificates module

The x/cert module is the protocol’s on-chain public key infrastructure. It anchors TLS certificates so that providers and tenants can mutually authenticate off-chain connections, with the ledger as the root of trust rather than a commercial certificate authority.

Certificates are issued and revoked by their owning accounts, giving every marketplace participant a self-service PKI. Both sides of a connection verify the peer’s certificate against chain state before workload data moves.

When a tenant’s client connects to a provider daemon endpoint — to send a manifest, fetch logs, or reach a deployed service — both sides verify the peer’s certificate against chain state.

Certificates are issued and revoked by their owning accounts, giving every marketplace participant a self-service PKI whose root of trust is the ledger rather than a commercial certificate authority. Revocation is recorded on-chain, so it takes effect for all future connection checks and is visible to every counterparty.

Leases are agreed on-chain but workloads are served off-chain. Without a shared PKI, the off-chain hop would be the weakest link — either unauthenticated or dependent on external CAs. Anchoring certificates in consensus lets any lease counterparty verify exactly who they are talking to.

ConceptDefinition
mTLSMutual TLS — both client and server authenticate, each verified against on-chain certificate state.
RevocationOn-chain invalidation of a certificate, effective for all future connection checks.
  1. Issue — Accounts issue certificates. Owning accounts create certificates for their endpoints and clients — self-service PKI.
  2. Present — Peers present on connect. Provider endpoints and tenant clients present chain-anchored certificates when connections open.
  3. Verify — Both sides check chain state. Mutual verification against on-chain records before any workload data moves.
  4. Revoke — Revocation is on-chain. Invalidation takes effect for all future connection checks, visible to every counterparty.
MessagePurpose
MsgCreateCertificateAn owning account issues a certificate for its endpoint or client.
MsgRevokeCertificateThe owning account revokes a certificate on-chain.
QueryPurpose
CertificatesChain-anchored certificates recorded for lookup during connection checks.
ModuleHow they interact
x/providerProvider endpoints present chain-anchored certificates to tenants.
x/deploymentTenant clients authenticate with certificates when delivering manifests.
x/marketLease counterparties are the identities certificates authenticate.

Why not just use public certificate authorities?

Section titled “Why not just use public certificate authorities?”

Leases are agreed on-chain but workloads are served off-chain. Anchoring certificates in consensus lets any lease counterparty verify exactly who they are talking to, without depending on external authorities for the protocol’s most sensitive hop.

Mutual TLS: both client and server authenticate, each verified against on-chain certificate state — the lease counterparties are the identities the certificates authenticate.

The owning account revokes the certificate on-chain, and revocation is effective for all future connection checks across the marketplace.