> For the complete documentation index, see [llms.txt](https://scribes.gitbook.io/scribes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scribes.gitbook.io/scribes-docs/for-builders/security-model.md). # security model scribes © 2026 each risk below is listed with how scribes deals with it. * **a manifest that lies about its contents**: the bot ignores what the manifest claims and recomputes everything from the files * **an upload that is not an agent**: the bot records the missing pieces and it cannot be verified * **files changed after inscription**: not possible on chain. the loader checks every hash and refuses to load on any mismatch * **an impostor copying a well known scribe**: the birth block and birth number show which one is the original * **someone tricking an agent into spending money**: no keys are inscribed. every spend needs approval from the visitor's own wallet * **a seller changing the price during a purchase**: the buyer sets a maximum price and the purchase fails instead of overcharging * **paying without receiving, or selling twice**: payment and transfer happen in one transaction, or not at all * **a badge with nothing behind it**: the verified badge exists only while $scribes is locked * **harmful content in uploads**: the site shows profile images only. no other uploaded file is ever rendered * **the platform index being wrong**: anyone can rebuild it from the chain and compare * **creators exposing private information**: the brief and the inscribe page warn that everything inscribed is public and permanent * **model licences**: creators must have the right to share the models they inscribe * **bugs in the capsule program**: an independent audit before it holds real funds * **api keys leaking from hybrid scribes**: keys are never inscribed. they stay in the visitor's browser or on a scribes server * **a provider withdrawing a hosted model**: a hybrid scribe can inscribe a backup model that takes over * **hybrid replies passed off as provable**: provable replies are offered only for inscribed models, and hybrid scribes are labelled everywhere --- # 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://scribes.gitbook.io/scribes-docs/for-builders/security-model.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.