Cryptographic Bill of Materials
Cryptography you can inventory. Transitions you can prove.
Talero turns the cryptographic rules of the network into a consensus-sealed, machine-verifiable inventory that every node confirms.
Machine-verifiable CBOMConsensus-sealedNode-confirmedTransition-aware
Public-safe is not unrestricted. This page explains the cryptographic mechanism without publishing exact release identifiers, cryptographic release values, keys or operational configuration.
A CBOM that participates in consensus
A conventional cryptographic inventory is often a report produced beside a system. Talero's consensus manifest makes the inventory part of the network agreement itself. It binds cryptographic algorithms, scheme and key-size profiles, protocol roles, signing domains and schemas into the rules every node checks.
The manifest is cryptographically sealed and tied to the chain timeline. The network can demonstrate which cryptographic rule set applied at a given block without publishing keys or release-identifying cryptographic values. Cryptography becomes auditable ledger context rather than undocumented implementation detail.
How the Talero mechanism works
1 · Inventory
The manifest describes the cryptographic schemes and roles that define the network rules.
2 · Agreement
Each node confirms the same manifest as part of its consensus configuration.
3 · Runtime evidence
Generated contracts expose the public runtime inventory: 265 RPC methods, 91 REST routes and 15 capabilities.
4 · Coordinated transition
A cryptographic change moves participants together to a new agreed inventory and ruleset.
What the cryptographic inventory covers
| Domain | Current cryptographic design | Auditable meaning |
|---|
| Validator and BFT evidence | ML-DSA-65 for validator identity, registration proof, HotStuff proposals, votes, quorum certificates, slashing evidence and finality-certificate formats | The post-quantum signature scheme is explicit by protocol role. |
| Transaction authorization | ECDSA secp256k1 for classic Ethereum transactions; ML-DSA-65 for native type 0x06 | The classical and post-quantum paths are distinguishable and coexist in one WorldState. |
| Checkpoint attestations | ML-DSA-65 | Checkpoint evidence remains independently verifiable after the quantum transition. |
| P2P sessions | Hybrid X25519 + ML-KEM-768 key exchange, ML-DSA-65 authentication and ChaCha20-Poly1305 application encryption | Key establishment, peer authentication and encrypted transport are separately identified. |
| Block production | TaleroHash using Keccak-256 plus memory | The quantum-resistant work function is part of the consensus inventory. |
| EVM verification | Experimental ML-DSA-65 verifier at 0x0000000000000000000000000000000000000903 | The verifier is labeled experimental and does not change classic account signatures. |
Crypto agility becomes a coordinated network capability
NIST defines crypto agility as the ability to replace and adapt cryptographic algorithms while preserving security and ongoing operation. Talero's coordinated manifest transitions give that principle a consensus-native form: a change is represented as an explicit move from one agreed cryptographic inventory to the next.
This makes change reviewable. An institution can reason about the algorithms, protocol domains and rule set associated with a network era instead of relying on an undated architecture diagram.
Why CBOM moved into the institutional agenda
Executive Order 14412
Signed June 22, 2026, it sets federal PQC migration deadlines and directs CISA with NIST to publish minimum CBOM elements that enable automated cryptographic-asset assessment.
CNSA 2.0
From January 1, 2027, new acquisitions for National Security Systems must be CNSA 2.0 compliant unless otherwise noted.
NIST crypto agility
NIST treats discovery, inventory and replaceability as core capabilities for PQC migration and future cryptographic transitions.
Talero is not claiming regulatory certification. It implements the technical property those frameworks increasingly demand: a cryptographic inventory that is machine-verifiable, attached to system operation and designed for transition.
Why this matters for long-lived programmable assets
Institutional and tokenized-asset systems need more than a statement that strong cryptography exists. They need to know which algorithms protected authorization, consensus evidence and transport, and when those rules changed.
Talero combines that auditability with EVM programmability. Its RWA contracts remain an experimental MVP inspired by ERC-3643, without a certified production deployment; the CBOM mechanism is the chain-level cryptographic foundation, not a claim of application-level compliance.
What this proves — and what it does not
- It proves agreement on an explicit cryptographic inventory and coordinated rule transitions.
- It does not turn classic ECDSA transactions or standard EVM accounts into post-quantum accounts.
- It does not imply that strict BFT finality is active; the architecture is tested and ready for activation, while strict activation is not armed in the deployed public testnet release.
- It is not an external security audit, regulatory certification or mainnet claim.
Official policy and standards references
United States policy
Executive Order 14412
Federal PQC deadlines and direction to define minimum CBOM elements.
National Security Systems
CNSA 2.0
NSA algorithm requirements and transition milestones.
Technical guidance
Crypto Agility
NIST definition, strategy and operational transition guidance.
