> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/protocol/utility-features/seralization-formats.md). # Seralization Formats Serialization in æternity defines the standardized binary formats used to encode different blockchain objects for critical operations like hashing, Merkle Patricia Tree insertion, and transaction signing. These formats ensure consistent data representation across the network, enabling reliable cryptographic operations and state management. The [Seralization documentation](/developer-documentation/protocol/serializations.md) provides detailed technical specifications for serializing all æternity blockchain objects, including blocks, transactions, accounts, smart contracts, and state trees. It covers RLP (Recursive Length Prefix) encoding specifications, version handling, and format changes across protocol upgrades like Roma, Fortuna, and Lima. The documentation is particularly thorough in detailing object tags, field specifications, and special type handling, making it an essential reference for developers working with æternity's data structures at a protocol level. --- # 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.aeternity.com/aeternity-developer-tools/protocol/utility-features/seralization-formats.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.