// Section 7.1 · Protocol
The Misbehaviour Taxonomy
Six categories. Increasing severity.
// 7.1 · the misbehaviour taxonomy · detection always lives at the coordination layer
SOFT OFFLINE
Fails to accept tasks for more than 24h without prior unstake notification
Coordinator heartbeat monitor
Fails to accept tasks for more than 24h without prior unstake notification
Coordinator heartbeat monitor
FAILED POE
Returns a result whose PoE hash does not match on reconstruction
Hash-commitment check
Returns a result whose PoE hash does not match on reconstruction
Hash-commitment check
WRONG RESULT
Returns valid PoE but the output is wrong, caught by redundant re-dispatch
Redundancy comparison (sampled second node)
Returns valid PoE but the output is wrong, caught by redundant re-dispatch
Redundancy comparison (sampled second node)
PROVABLY MALICIOUS
Returns deliberately corrupted, manipulated, or fabricated data
Forensic analysis on returned payload
Returns deliberately corrupted, manipulated, or fabricated data
Forensic analysis on returned payload
COLLUSION
Multiple nodes return matching wrong results to bypass the redundancy check
Statistical analysis of result agreement
Multiple nodes return matching wrong results to bypass the redundancy check
Statistical analysis of result agreement
SYBIL IDENTITY
Single operator runs multiple node identities to capture more work than allowed
Behavioural fingerprinting, IP / hardware overlap
Single operator runs multiple node identities to capture more work than allowed
Behavioural fingerprinting, IP / hardware overlap
Detection vs enforcement
// detection is invariant · enforcement evolves over time
Detection
Lives at the coordination layer. The same mechanism applies throughout. Hash check, sampled re-dispatch, statistical analysis, behavioural fingerprinting, reputation tracking.
see §7.5 for how each scales
Enforcement
Uptime-based, no slashing. A node that fails liveness or validation earns nothing while offline; its share of the stream redistributes to online nodes. Bad results are eliminated by Proof-of-Execution plus sampled redundant re-dispatch. Staked principal is never seized.
see §7.2