> For the complete documentation index, see [llms.txt](https://docs.portaldefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portaldefi.com/validators/auction.md). # Auction For every epoch, there are going to be a limited number of Validator slots (42 in Portal Network). Any potential Validator interested in participating needs to win the slot in the Auction by participating in the bidding process. Auction process starts every epoch and continues during the entire epoch period till the end of epoch. At the end of the current epoch, all highest bidders (who staked more $XPORT tokens) will win the 42 slots. After winning, Validators need to participate in the keygen ceremony and are selected as Active Validator set for the next Epoch. The existing Validator set transfers their keys to the current Active Validator Set chosen. Validators participating in bids commit their $XPORT tokens for the auction's entirety and are restricted from shifting their status to Inactive (no current stake). Inactive Validators lacking a current bond retain the ability to withdraw funds as usual but can switch their status to bidding during the ongoing auction. --- # 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://docs.portaldefi.com/validators/auction.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.