# Proof of Productivity

## Overview

The Proof of Productivity is periodically executed, and its result (negative or positive) leads to and influences the reward distribution based on a multi-sig token re-issuance process on liquid.

{% hint style="info" %}
Under the assumption that a single point of notarized data (CID) exposes and thus discloses no relevant information, PoP can be viewed and interpreted as a multi-round zero-knowledge proof. 
{% endhint %}

## Stages of Pop

The following stages of PoP exist:

1. [**Actor Selection**](/rddl-network/basics/proof-of-productivity/actor-selection.md)**:** The block-creating validator selects the PoP actors and initiates the PoP with the selected actors
2. [**Challenge-Response**](/rddl-network/basics/proof-of-productivity/challenge-response.md): The challenger and challengee execute/perform the PoP.
3. [**Rewards**](/rddl-network/basics/proof-of-productivity/rewards.md): The validators evaluate the notarized PoP Result and issue RDDL tokens as rewards.

{% hint style="info" %}
The current implementation is based on MQTT. The goal is to switch XMPP to guarantee a privacy-preserving PoP.
{% endhint %}


---

# 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://docs.rddl.io/rddl-network/basics/proof-of-productivity.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.