> For the complete documentation index, see [llms.txt](https://tokens-economy.gitbook.io/consensus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tokens-economy.gitbook.io/consensus/chain-based-others/proof-of-devotion.md). # Proof of Devotion Similar to POI, the PoD selects the accounts with high influence. All accounts are ranked according to their liquidity and propagation (Nebulas Rank). #### Algorithm * Top-ranked accounts are selected * Chosen accounts pay deposit and are qualified as the blocks Validators (Validators Set is dynamic, changes in Set may occur after Epoch change.) * Algorithm pseudo-randomly chooses block Proposer * After a new block is proposed, Validators Set (each Validator is charged a deposit) participate in a round of BFT-Style voting to verify block (1. Prepare stage -> 2. Commit Stage. Validators should have > 2/3 of total deposits to validate Block) * Block is added. Block rewards : each Validator rewarded with 1 NAS. #### Used in * Nebula * [whitepaper](https://nebulas.io/docs/NebulasTechnicalWhitepaper.pdf) * [Github](https://github.com/nebulasio/wiki/wiki) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://tokens-economy.gitbook.io/consensus/chain-based-others/proof-of-devotion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.