Proof of Trusted Behavior needs evidence that another participant can independently check.
Conflicting signatures become a proof
Two authenticated votes from the same validator, for the same chain, height, round, phase and committee, but different values, form a double-vote proof. The collector retains bounded evidence. Validator nodes save the first verified proof for each registered identity in a durable outbox.
The CLI can create and independently verify these proofs against a trusted genesis and key registry.
Scoring remains experimental
A deterministic tracker replays finalized certificates and evaluates a bounded age-based candidate weight. A missing signature in one quorum certificate is not proof of downtime, so it is not treated as misconduct.
This work does not activate new weights, remove validators or introduce automatic on-chain slashing. Those steps require a finalized evidence-inclusion rule, committee transitions and further security analysis.
Help test the assumptions
Useful contributions include reproducible restart tests, conflicting-vote cases, network partitions and integration feedback. Comparative speed or security claims require comparable benchmarks and independent review.