# 4.2 Proof of Service (PoSv) Protocol

PoSv converts physical work into cryptographically auditable on-chain revenue events, eliminating reliance on off-chain oracles.

#### Protocol Sequence

1. Client submits API request with session nonce and pre-authorized $QBT fee
2. Protocol contract assigns request to eligible node (stake-weighted, geographically distributed)
3. Node executes task: QRNG entropy generation or PQC signing
4. Node generates PQC-signed receipt:\
   { timestamp | node\_id | request\_hash | output\_commitment }
5. Receipt is submitted to the on-chain validator contract
6. Validator verifies: registered node, valid signature, timestamp bounds, request hash match
7. Upon validation, fee is released: 15% burn, 40% operator, 45% Vault
8. Settlement event is recorded as finalized receivables in Vault accounting


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://railquant.gitbook.io/quantarail/4.-technical-advantage-hardware-based-trust/4.2-proof-of-service-posv-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.