# Abstract This technical document proposes a new blockchain architecture based on Proof of Engagement (PoE) - A proof for verifying engagement among games developed by the developers and the end user, and the passage of time between events, while recording transactions in terms of events related to the movement of digital assets in the Cypher blockchain ecosystem. (PoE) Consensus protocol plays a vital role in the functioning of a blockchain. At present, mainstream consensus protocol includes proof of stake (PoS), proof of work (PoW), and delegated proof of stake (DPoS). PoW, as we know is widely used in virtual currencies, and results in the consumption of energy significantly; proof of stake (PoS) and delegated proof of stake (DPoS) are proposed to reduce the energy waste caused by PoW protocol, but their disadvantage is that they tend to create the Matthew Effect (ME): wherein “the rich get richer.” To balance this unbalanced power of new nodes and elder ones, this technical paper proposes a flexible protocol mechanism called proof of engagement (PoE), based on the user engagement activity and contribution of network nodes by game developers. In our sandbox experiments, we tested the profit changes under PoW, PoS, and PoE. The results illustrate that it is easier for new nodes to accumulate their rewards under a PoE protocol than under PoW or PoS, and reduce the negative impacts of ME. [Reference and credits here](https://www.hindawi.com/journals/wcmc/2021/6185910/) --- # 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/abstract.md?ask= ``` 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.