Security
20 articles
Payments for machinesWhat a receipt for AI work proves
Agent payment schemes prove that a payment was made and that someone consented to it. Inference receipts prove that a machine produced an answer. Neither alone proves that the money matched the work. What each kind of evidence covers, where the gap is, and how Tenzro binds the two.
6 min read
ConsensusInside Tenzro's Consensus: DAG-Based BFT for a Network of Machines
How Tenzro orders transactions with a DAG protocol, makes finality portable with hardware-signed checkpoint certificates, hands over between committees at epoch boundaries, and checks the code against a formal model step by step.
6 min read
Enterprise AIAgentic AI in the Enterprise: Delegation You Can Audit
When agents call tools and spend money, governance has to move from policy documents into the systems that authorise each action. A delegation model, a control checklist and the records an auditor will ask for.
5 min read
SecuritySecuring the AI Model Supply Chain, From Weights to Serving
A model file is executable risk: it can carry code, be swapped in transit or be served by a machine that is not what it claims. A layered control set for model provenance, safe formats, signed releases and attested serving.
5 min read
Financial servicesAI in Financial Services: Records an Examiner Can Verify
Banks, insurers and asset managers are moving AI into credit, claims, compliance and operations. Supervisors in the EU, UK, US and Singapore expect model inventories, third-party oversight and records. What a verifiable inference record should contain, and how to keep it.
4 min read
HealthcareAI in Healthcare: When the Data Cannot Move, Move the Model
Clinical and research data is among the most regulated anywhere. Three patterns that bring AI to health data without moving it (local serving, confidential computing and federated training) and the evidence each one should produce.
4 min read
ManufacturingAI on the Factory Floor: Edge Inference and Machine Identity
Factories need AI that keeps running when the internet does not, on machines that can prove what they are. How to place inference on the shop floor, anchor every device in hardware, and meet the security regimes now arriving for industrial products.
4 min read
Confidential computingConfidential Computing for Regulated AI: What Attestation Proves
TEE sessions and remote attestation let a regulated workload run on someone else's hardware with evidence of what code ran. What a report actually proves, what it cannot, and how Tenzro verifies, binds and routes confidential work.
5 min read
Data residencyData residency by design: pinning AI work to a jurisdiction
Residency rules for AI are moving from contract clauses into the request path. This article explains how to make jurisdiction a routing constraint that fails closed, what evidence a signed record of locality can and cannot give you, and how the rules differ across the EU, UK, MENA and APAC.
6 min read
SafetyDesigning Safe Harnesses: Scopes, Limits, Expiry and Revocation
Prompt injection will sometimes succeed, so an agent's safety has to live outside the model. How Tenzro bounds every delegated agent with consensus-enforced scopes, spending limits, expiry, step-up approval and revocation, with an accountable root behind each one.
5 min read
Sovereign AIEU AI Act, NIS2 and the Data Act: a guide for AI operators
Three EU laws now shape how AI infrastructure is run in Europe. This guide sets out the dates that apply after the 2026 Digital Omnibus on AI, the obligations that reach operators, and the evidence worth producing by default.
7 min read
Generative mediaGenerative Media Pipelines: Right Hardware, Pay Per Result
Image, video and audio generation have cost profiles unlike chat. How to route each job to hardware that fits it, meter it in units that match the work, check licence territory and mark outputs for provenance.
5 min read
Distributed computingGPU operators: sell compute on verifiable service levels
Conventional cloud SLAs are measured by the provider, and the customer has to claim any credit. On an open market of independent GPU operators, availability and output have to be verified by someone else, and payment has to follow the verification. This article explains how that works and what it changes for operators.
6 min read
Hardware identityDevices that join a network at first boot, with hardware identity
For hardware manufacturers, the identity a device carries out of the factory decides what it can do in the field. This article covers which identifiers can anchor a machine and which cannot, why keys belong sealed to the hardware, and how devices can join an open AI network from the first time they power on.
6 min read
Hardware identityHardware-Rooted Identity for Machines: TPMs, Enclaves and Passkeys
A key file can be copied, and a copied key is a second machine nobody knows about. Why Tenzro derives every machine and person's identity from keys that never leave hardware, and how that works on servers, laptops and boards without a TPM.
5 min read
Open modelsOpen models need open infrastructure: provenance and licences
Once open weights are released, the builder loses sight of how they are served. This article covers what model builders should expect from the infrastructure that serves their work: proof of which weights ran, licence terms enforced in the serving path, gated access that holds, and attribution that reaches the user.
5 min read
SecurityPreparing AI Infrastructure for Post-Quantum Cryptography
NIST's ML-KEM, ML-DSA and SLH-DSA standards are final, the IETF has standardised hybrid key exchange for TLS, and the US and EU have set dates. A practical migration plan for AI infrastructure, and how Tenzro applies hybrid post-quantum keys today.
5 min read
Model routingRouting Across Many Providers, and Why Receipts Must Be Verifiable
A model router chooses on price, latency and standing, hedges the slow tail and fails over in seconds. None of that is trustworthy unless each answer comes with a receipt a third party can check. How Tenzro does both.
5 min read
Hardware identityTDIP: one identity protocol for humans and machines
Humans, delegated agents and autonomous agents under one W3C DID method, with keys rooted in passkeys and device hardware. Why agents need an identity of their own.
2 min read
Confidential computingTEE security: verified attestation across vendors
Intel TDX, AMD SEV-SNP, AWS Nitro and NVIDIA confidential GPUs, each attestation verified to its vendor root. Attestation is evidence; keys stay in their owners' hardware.
2 min read