Seeing a “This Connection Is Not Private” warning?

Some corporate networks and security tools (such as Cisco Umbrella) intercept HTTPS traffic and replace the site’s certificate with their own. If you manage that filter, whitelist actum.network and activechain.dev to stop the certificate warning. The site itself is served over a valid Cloudflare certificate from our side.

A clean-slate trust layer for the agentic age

The internet is becoming intelligent.
Its trust layer is not.

Actum is post-quantum from day one: a protocol for verifiable identity, programmable authorization, smart contracts, and accountable AI.

Why Actum Read the architecture

Protocol design · Pre-testnet · Open research and implementation

Choose a path

01Identity & authorityPersistent principals, selective credentials, and capabilities that narrow through delegation.02A coherent protocolOne typed boundary for authorization, consensus, private objects, and proof admission.03Privacy & evidenceProve what a policy requires without exposing the underlying record.04Accountable AIBind agents and outputs to exact permissions, inputs, models, budgets, and evidence.

The protocol in one sentence

Specialized actors can compute, build, prove, store, and serve—without becoming authorities users must trust.

New protocol functionality

PQ payments and portable identity now share one authorization boundary.

The implementation connects real post-quantum cash authorization with holder-owned credential presentations. Both remain bounded by explicit proof, policy, and finality checks—not provider assertions or public identity records.

PQ-native payments

ML-DSA-authorized cash with proof-aware settlement.

Native Coin Cells, bounded payment sessions, authenticated CashAIR transitions, and the ActiveBridge SDK keep external payment events distinct from chain finality.

Implemented developer boundary · staged pilots and independent review remainVCIssuer identity integration

Issue portable credentials. Authorize with minimal facts.

OpenID4VCI SD-JWT VC and mdoc credentials stay with the holder; Actum admits only a scoped verifier result tied to the exact action and policy.

Integration implemented · physical-device qualification and review remain

Pre-testnet functionality. No claim of a live production payment rail, provider partnership, identity assurance, or completed security qualification.