> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/architecture/consensus/vote-stapling.md). # Vote Stapling A vote staple is the unit of distribution, creating a permanent voting context by combining multiple [blocks](/components/blocks.md) to all be voted on and published to the network at once. Nodes transmit vote staples over the network and clients publish vote staples. If one block in the staple is invalid, all blocks are rejected and must be sent back through the voting process without the invalid operation(s). Keeping the blocks and [votes](/architecture/consensus/votes.md) together increases efficiency and relieves the network from locating multiple pieces of data on the same operation. A staple is constructed from at least one block, and at least one vote. All votes within a single staple must be for the same blocks in the same order as the staple was constructed with. Additionally, a staple cannot contain mixed temporary and permanent votes. To maximize efficiency, the network uses compressed staples. The more similar the included blocks and votes contents are, the more the staple can be compressed. --- # 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.keeta.com/architecture/consensus/vote-stapling.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.