> For the complete documentation index, see [llms.txt](https://sg.laine.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sg.laine.one/practicalities/proposal-collateral.md). # Proposal collateral To prevent abuse and spam users creating a proposal could be asked to provide collateral. This concept exists on Cosmos for instance. The collateral would begin at a fixed nominal amount, e.g. 10 SOL, and increase with every active non-resolved proposal that exists, thus creating a disincentive to spam new proposals before older ones are voted upon. The proposer would receive back their full collateral regardless of whether the proposal passes or fails, except where the plurality has voted for ["No with veto"](/practicalities/voting-options-and-slashing.md), this is a dissenting vote that further wants to slash the collateral of the proposer, to be used for proposals that are extremely bad, harmful or time-wasting. --- # 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://sg.laine.one/practicalities/proposal-collateral.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.