// Section 4.4 · Protocol
Reputation Weighting
Planned, not yet built. Constant 1.0 at launch.
// 4.4 · reputation weighting · signal 4 of 4
Caveat·At launch reputation is constant 1.0
Once reputation ships
// ties broken at equal capability and capacity · eligibility weighted for higher-value work
Once reputation ships, it breaks ties at equal capability and capacity. It also influences eligibility for higher-value work. A node with strong reputation gets first claim on the heaviest, highest-priority work; a node rebuilding from a bad streak picks up lighter work until validation history rebuilds.
Three inputs
// uptime · completion · validation success
Fraction of the 30-day window the node was in READY or EXECUTING state. Heartbeat-driven; gaps count as offline.
Validated returns divided by dispatched work. The items the node accepted and returned a valid result for, divided by all items dispatched to the node.
Rolling 90-day rate of validated returns vs returns rejected by hash check or redundant re-dispatch.
The reputation multiplier
// full table in §8.6 reward formula
The reputation multiplier scales the operator reward per validated return (§8.6). It also gates eligibility for higher-value work in the scheduler.
Tie-breaking flow
// live now vs planned behaviour at the tie-breaking step
All nodes carry reputation 1.0. At equal capability and capacity, the scheduler dispatches to whichever node entered the candidate pool first. Behaviour is deterministic; enforcement is uptime plus PoE plus sampled re-dispatch.
Reputation breaks ties at equal capability and capacity. Work above a value threshold is restricted to nodes above a reputation threshold. A bad streak lowers reputation, which lowers dispatch priority and can drop a node from the active set. It never seizes stake; the loop self-corrects through routing, not slashing.