Consensus
PoW production before scheduled strict BFT finality.
Talero currently produces blocks with proof of work. A strict precommit-QC finality rule is configured for height 115200 but is not active while the chain remains below that height.
PoW active
BFT height 115200
Pre-activation bootstrap lag
No payout-grade claim
Scheduled is not active. Always compare the current head with the activation height and inspect the returned finality class.
Current consensus phase
The public testnet is below the configured strict-BFT activation height. The node implements ML-DSA-65 validator identities, proposal and vote formats, precommit quorum certificates and evidence handling, but the observed public node currently reports no active validator committee and inactive validator finality.
The configured fork bft_strict_precommit_qc is enabled for height 115200. Until the chain reaches that height and a valid quorum is active, applications must retain pre-activation semantics.
Read finality precisely
talero_finalizedHead is the canonical public finality response, but consumers must inspect its semantic fields. Before strict BFT activation, the observed response uses finalityClass: bootstrap_lag, enforced: false and payoutGrade: false. It is a lag-policy checkpoint, not proof of irreversible BFT settlement.
Status, estimates, wallet finality and PoQ signals remain diagnostic or advisory. Pool payouts apply their own documented maturity and canonical-chain safety controls.
Activation-safe client logic
- Read the current chain head.
- Read the configured strict activation height.
- Inspect the finality class and enforcement fields returned for the decision.
- Require an explicitly verified strict-BFT semantic before displaying “BFT finalized” or using it as economic finality.
Do not hard-code the present head height: it changes continuously. Do not infer activation solely from a feature being compiled into the node.
Stable consensus parameters
| Parameter |
Value |
| Target block time |
8 seconds |
| Strict BFT activation |
Height 115200 |
| Maximum active validator set |
64 |
| Minimum BFT threshold |
4 |
| Maximum validator registry |
2,048 |
| Epoch |
1,000 blocks |