> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/6.-transaction-model/6.6-wire-format-encoding-and-serialization-roadmap.md).

# 6.6 - Wire Format, Encoding & Serialization Roadmap

All on-wire transaction serialization currently uses **`bincode`** (binary, deterministic Rust serialization). Payloads are typed via a Rust enum (`TokenTransfer`, `NaaMint`, `NaaTransfer`, etc.), with future variants added as protocol phases mature.

**Wire Format Layout**

| Field             | Size            | Notes                                        |
| ----------------- | --------------- | -------------------------------------------- |
| Version Flag      | 1 byte          | Schema version selector                      |
| Sender Public Key | 1 + 1,312 bytes | Flag byte (§4.7) + Dilithium2 pubkey         |
| Nonce             | 8 bytes         | `u64` monotonic counter                      |
| Payload           | Variable        | Encoded enum variant                         |
| Signature         | 1 + 2,420 bytes | Flag byte + Dilithium2 sig over BLAKE2b hash |

A native `$POLA` transfer totals **\~10 KB on the wire**, driven by post-quantum signature sizes. The payload itself remains lightweight. Schema versioning follows enum-variant conventions: unknown variants trigger safe-fail rejection at decode time.


---

# 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://polarischain-1.gitbook.io/polarischain/6.-transaction-model/6.6-wire-format-encoding-and-serialization-roadmap.md?ask=<question>&goal=<endgoal>
```

`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.