> 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/8.-network-layer-and-protocol-operations/8.5-transaction-submission-protocol.md).

# 8.5 - Transaction Submission Protocol

External clients (wallets, SDKs, institutional gateways) submit transactions via a dedicated TCP listener optimized for high-throughput, persistent sessions:

1. **Handshake:** Client sends an 8-byte header (magic + version + reserved). Server responds with a single-byte registration status.
2. **Payload Exchange:** Client sends a 4-byte big-endian length prefix followed by the transaction payload. Server replies with a status byte: `accepted`, `queue-full` (client must back off), or `fatal` (oversized/unsupported version).
3. **Session Persistence:** Connections remain open for the session lifetime. Clients implement exponential backoff on `queue-full` responses without reconnecting.

This versioned, persistent-submission model eliminates the connection-per-transaction overhead of legacy designs, preventing TCP RST storms and stale-transaction drains under sustained load.


---

# 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/8.-network-layer-and-protocol-operations/8.5-transaction-submission-protocol.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.