Capability matrix
Fifteen capabilities. Every status explicit.
The runtime declares what is active, advisory, experimental, supported or unavailable — with maturity and exposure attached.
15 capabilitiesTestnet labelsPrototype labelsExplicit unsupported state
Public-safe is not unrestricted. Privacy, safe-mode, read-only, quota, role and gateway policies can still mask or deny a listed surface.
Capability matrix
| Capability | Status | Maturity | Exposure | Public wording |
|---|
| EVM execution | active | testnet | mixed | Execution is active; RPC exposure depends on policy. |
| Post-quantum P2P transport | active | testnet | internal only | Node transport is authenticated and encrypted. |
| PoQ advisory certification | advisory | testnet | mixed | Consultative, non-consensus and non-blocking. |
| PoS finality | active | testnet | mixed | The surface and protocol are tested; strict BFT activation is not armed in the deployed release. |
| PoW block production | active | testnet | pool | Production is active through the Talero pool/getwork interface. |
| ML-DSA-65 EVM verification precompile | experimental | prototype | internal only | Experimental verifier at 0x0000000000000000000000000000000000000903. |
| Public privacy surface policy | active | testnet | mixed | Address-sensitive reads remain policy-gated. |
| Runtime RPC policy matrix | active | testnet | public | Classifies the runtime surface by access profile. |
| Runtime safe mode | active | testnet | mixed | Status is observable; control commands remain restricted. |
| Honeytrap observation | active | testnet | trusted | Available on a trusted surface; operational configuration is not public. |
| Watchtower status | active | testnet | mixed | A public-safe status exists; configuration and notifications are restricted. |
| Selective disclosure balance threshold | experimental | prototype | mixed | Not a canonical-state membership proof by default. |
| Direct validator administration lifecycle | development/admin only | prototype | admin | Not a public production workflow. |
| EVM staking bridge | unsupported | prototype | internal only | Not supported and not wired. |
| Validator runtime transaction lifecycle | supported | testnet | private write endpoint | Supported through runtime transactions on a private write endpoint. |
How to read the labels
- Active means the capability exists at runtime; it does not override exposure policy or imply external certification.
- Advisory means non-consensus and non-blocking.
- Experimental / prototype identifies an early integration surface.
- Unsupported means the path is not wired as a supported capability.
