> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/developers/going-to-production/production-checklist.md).

# Production checklist

What to verify before launching a Lighter integration.

## Environment

* [ ] Tested end to end on **testnet** (`https://testnet.zklighter.elliot.ai`, chain ID `300`). See [Environments & endpoints](/developers/getting-started/environments.md).
* [ ] Mainnet config uses chain ID `304` and the mainnet base URL
* [ ] Market IDs and decimals are loaded from `orderBookDetails`, not hard-coded
* [ ] `wasm_exec.js` and `lighter-signer.wasm` come from the same Go build

## Keys & security

* [ ] Your app uses a dedicated API key index (4–254) that won't clash with others
* [ ] API private keys are encrypted at rest (keychain / KMS); never logged
* [ ] Your own keys never ship to a browser or mobile bundle
* [ ] The `bridge.lighter.xyz` builder key is used server-side only
* [ ] Read-only tokens are used wherever trading isn't needed (analytics, AI agents)
* [ ] Auth tokens are refreshed before their expiry (max 8 hours)

## Orders

* [ ] Prices and sizes converted with the market's decimals, and checked against minimums
* [ ] Market orders use a sensible worst price (slippage limit)
* [ ] `clientOrderIndex` values are unique across all markets
* [ ] `orderExpiry` is between 5 minutes and 30 days (or `0` for IOC)
* [ ] Execution is confirmed via WebSocket or `tx` lookup, not assumed from `code: 200`

## Nonces

* [ ] Sends per API key are serialized (or you use `skipNonce` deliberately)
* [ ] Retries follow [Retrying safely](/developers/getting-started/core-concepts.md#retrying-safely): check the tx status before re-signing
* [ ] Separate API keys for independent workloads

## Reliability

* [ ] WebSocket keepalive (a frame at least every 2 minutes) and automatic reconnect + resubscribe
* [ ] Order book continuity check (`begin_nonce` = previous `nonce`)
* [ ] Exponential backoff on HTTP 429/405
* [ ] Requests authenticated to use L1-based rate limits
* [ ] Tier chosen deliberately (Standard's 60 req/min is easy to hit). See [Account Types](/developers/reference/account-types.md).

## Money movement

* [ ] Deposit minimums shown to users (with slippage buffer)
* [ ] UDA `blocked` flag respected
* [ ] Transfer fees fetched from `transferFeeInfo` right before signing

## Partner fees

* [ ] Clients are on Plus or Premium/Advanced before non-zero integrator fees are attached
* [ ] Fees ≤ approved maximums ≤ `systemConfig` caps
* [ ] Re-approval flow before `approvalExpiry`

## Ops

* [ ] Subscribed to the [API Telegram channel](https://t.me/+4OylVDvI0z9lZDFk) / `#api-updates` on [Discord](https://discord.gg/lighterxyz)
* [ ] Contact channel with Lighter set up (Discord `#support`)


---

# 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.lighter.xyz/developers/going-to-production/production-checklist.md?ask=<question>&goal=<user_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.