// Section 5.5 · Protocol
The Validator Model
The coordination layer is the validator.
// 5.5 · the launch validator model · centralised by design
Caveat·Centralised validation, by design
Two checks before settlement
// hash reconstruction + sampled re-dispatch
Reconstruct and compare.
Coordinator recomputes SHA-256(request_id, result, node_id) using the returned values, compares against the PoE the node submitted. Mismatches reject the result outright. This catches every fabricated PoE.
A fraction runs on a second node.
A configurable share of validated requests is re-dispatched to a second, independently selected node. Both commitments are compared. Disagreement triggers a third dispatch and a majority decision. Persistent disagreement flags every party for review.
Escalation flow
// disagreement triggers a third dispatch · persistent disagreement flags for review
Two independently selected nodes execute the same request. Both return, sign, and generate PoE.
Coordinator compares PoEs and results. If they disagree, a third independently selected node runs the request.
If the third agrees with one of the first two, majority decides. If all three disagree, every party is flagged for review.
Launch vs planned
// centralised now · validator quorum next
Coordinator as validator
Single coordinator. Hash check and sampled re-dispatch. Fast, simple, honest about the centralisation.
Decentralised validator quorum
Independent third-party validators staking $PRLX to participate. Multi-validator quorum overlays the re-dispatch layer. Same primitives, decentralised enforcement.