> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/3.-cryptographic-foundations/3.6-leader-election-and-predictability-security-model.md). # 3.6 - Leader Election & Predictability Security Model Leader selection uses a **stake-weighted, deterministic random function** keyed exclusively to the round number. This approach eliminates the computational overhead and verification latency of Verifiable Random Functions (VRFs) while preserving BFT security. Predictable leader election does not compromise safety: invalid or censored anchors are rejected during the round-2/round-3 certification phase. Targeted attacks against a known leader may delay liveness but cannot violate safety; the protocol automatically advances to the next scheduled leader via standard timeout mechanisms. Reputation-based leader rotation will be introduced post-PoS activation, using performance telemetry to dynamically deprioritize underperforming or unresponsive validators. --- # 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://polarischain-1.gitbook.io/polarischain/3.-cryptographic-foundations/3.6-leader-election-and-predictability-security-model.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.