Talero defines ML-DSA-65 validator identity and BFT evidence, while strict precommit-QC finality is scheduled at height 115200 and is not active on the current pre-activation chain.
Validator support is not validator activation. Compiled message formats do not prove that a quorum is active or that a block is strictly finalized.
The node defines ML-DSA-65 registration proof of possession, validator identity, proposal, vote, quorum-certificate, slashing and finality-certificate formats. These are protocol capabilities. Their effective assurance depends on an active validator set, quorum and the current consensus phase.
The observed public runtime is below height 115200, reports zero active validators and reports validator finality as inactive. The published finalized head is currently classified as bootstrap_lag, with enforcement and payout-grade flags false. It must not be labeled strict BFT finality.
| Parameter | Value |
|---|---|
| Strict BFT activation height | 115200 |
| Maximum active set | 64 |
| Maximum registry | 2,048 |
| Minimum BFT threshold | 4 |
| Epoch | 1,000 blocks |
| Reward claim window | 360 epochs |
Validator lifecycle writes are restricted workflows and are not exposed as anonymous administration RPC. Wallet features related to validator operations require an authenticated session and remain subject to live capability and write-governance checks. The EVM staking bridge is not documented as a supported public integration path.
