> For the complete documentation index, see [llms.txt](https://docs.burve.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.burve.fi/technicals/omni-pool-details/vertex.md). # Vertex A vertex encapsulates the rehypothecation earnings of a token. Every token in the protocol (because the earnings for the protocol itself) are kept in a Vertex which then fowards those token deposits into either one or two vaults through a Vault Proxy. Each vertex is identified by a VertexId which is a product type on an array index and the one-hot encoding of that array index. The bottom 8 bits are the array index which is used extensively throughout the protocol. The top 16 bits is the one hot encoding which we use to interact with the ClosureId. The ClosureId is simply the bitwise union of the one-hot of all the vertices for all the tokens in its subset. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.burve.fi/technicals/omni-pool-details/vertex.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.