# Proof of Engagement {PoE}

Since PoE is not just one algorithm from game theory, but a solution space achieved by combining different models into a solution that best fits the current state of the chain, there is a need for both flexibility and evolution in the implementation. Given this, we propose to construct PoE via multiple Smart contracts, with clearly defined interfaces and a clean composition model. This will allow us to adjust individual contracts, swap out implementations, and even rewire the composition model as we explore the PoE solution space.

We propose to get to a working foundational PoE implementation with the following roadmap, where each stage builds on the last:

{% code overflow="wrap" lineNumbers="true" %}

```
// Controlling validator set with a privileged contract
// Implement PoE via modified multisig contracts
// Bootstrapping
// Implement PoS via token-locking contract
// Distribute rewards to validators (Rewards per block)
// Manage Slashing feedback when evidence is submitted, slashing done in contract
// PoE as mixer implementations
// Governance control and voting power
```

{% endcode %}

![](/files/mYZCAX5prThHliRqmcMM)


---

# 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://support-168.gitbook.io/cypher-blockchain-whitepaper-v1.0/proof-of-engagement-poe.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.