> 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/on-chain-format.md). # on chain format scribes © 2026 every part of a scribe is written to solana. this page covers how. ### chunks files are split into pieces of about one kilobyte. each piece goes in its own transaction and carries: * the hash of the file it belongs to * its position in that file * its data the memo prefix `scribes:v1:` marks a transaction as a scribes transaction. pieces can land in any order. the file is rebuilt by position and checked against its hash. ### shared models a model is inscribed once. any later scribe that uses it points to it by hash and does not write it again. the first scribe to inscribe a model gets that model's **autograph**. ### personality account the personality is also stored in an account owned by the scribes program. the program has no instruction that can close or edit that account, and any standard solana connection can read it. ### listing profile the display name, profile image (jpeg or png, with a size cap) and optional wallet address are inscribed with the scribe. the wallet field takes a wallet address only. private keys are never asked for. ### birth transaction the last transaction ties everything together. it: * points to the manifest * includes the inscription payment * optionally locks $scribes into a new capsule * is signed by the owner the block it lands in is the **birth block**. the indexer gives out the **birth number** by counting births in chain order. > exact byte layouts, size caps and the program address will be published with the program. --- # 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/on-chain-format.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.