gm

We’ll be pruning unfilled (cancelled) orders from the order history table, except the last 3000. All other orders in order history remain untouched.

gm

- We are doing a network upgrade on Sunday, Oct 26th at 11AM UTC. We are updating our prover services. Downtime should be under 15 minutes. Please manage your positions in advance.

- We’re adjusting $LAUNCHCOIN today at 5PM UTC and moving the market to reduce-only mode. This change is being made earlier to ensure a smoother experience as other venues/oracles delist. Delisting will happen tomorrow at 11AM UTC.

gm, new documentation on Orders and Matching

https://docs.lighter.xyz/perpetual-futures/orders-and-matching

gm, re: Invalid Nonce

If you're getting Invalid Nonce errors, make sure the orders you're submitting are within margin. Order margin checks will be handled as app errors in the next upgrade.

gm

We're doing a quick network upgrade October 28, 2025 at 1:10 PM UTC (in 10 mins). Downtime should be under 5 minutes.

we’ve identified bot activity causing unusually high TPS
our team is implementing fixes and will deploy a solution shortly

we should be good now. report soon.

Report on today's disruption

We experienced a service disruption between 19:40 and 20:01 UTC today that affected API transactions. The issue has been resolved, and all systems are back to normal. During this time, the core exchange and committer continued operating as expected, but the API server was unable to process transactions properly.

Before markets became volatile, we noticed that roughly one-third of all transactions were coming from what appeared to be automated bots engaged in wash trading. Even in low-volatility periods, this suspicious activity was driving unusually high TPS and contributing to instability. Later on, the markets went down quickly during the disruption.

We take full responsibility for the incident. All affected transactions have now been processed, and LLP orders were not impacted.

What we are doing:
- We’re banning the identified bot accounts, revoking any associated points
- Reassessing our API volume quota and rate limit mechanisms to strengthen stability
- Putting in better retry logic in our API servers
- Making users whole with USDC compensations

If you were affected by this issue, please fill out the form provided. There’s no need to open a support ticket if it relates to this incident.
Form: https://forms.gle/cJ1Wsiqzd8Ve3p5Z8

We're doing a quick network upgrade on November 2nd at 11AM UTC. Downtime should be under 10 minutes. Manage your positions in advance.

We’re delisting $Ai16z and will settle all open positions at mark price on November 4, 2025 at 7:00 PM UTC. Please review and manage your positions in that market.

We'll deploy the following modifications for Premium Accounts on November 4, 2025 at 1:00 PM UTC:

- We’ll be updating the Premium Account Tx rate limit. Premium accounts will earn 1 Tx per $5 in trading volume (previously 1 Tx per $1). Tx accumulation will pause once an account reaches 5,000,000 Tx
- Endpoints will directly return your remaining transaction allowance. WS sendTx and sendBatchTx will also return the remaining volume quota

We’re doing a network upgrade on November 6, 2025 at 2:15 PM UTC (in 45 mins). The system will be back online before market open.

Updates:

- Added nonce field on order_book WebSocket channel that directly align with the matching engine state. (Premium Only)
- Added volume_quota_remaining field on both WebSocket and API response of /sendTx and /sendBatchTx. You can directly track you remaining quota from that numeric field

Update:

We’ll retire the ‘transaction’ and ‘executed_transaction’ WebSocket channels on Tuesday, November 11 at 3 PM UTC

Update:

You can now match your client_order_id on trades using the ask_client_id or bid_client_id fields.

We're doing a network upgrade on November 13, 2025 at 9:30 PM UTC. Downtime should be under 10 minutes. Manage your positions in advance, orders will not get placed.

Update:

Premium Accounts will earn 1 Tx per $10 in trading volume (previously 1 Tx per $5). Tx accumulation still pauses once an account reaches 5,000,000 Tx.

Email and JSON subscription to maintenance updates:

https://status.lighter.xyz/

Updates:

We are deprecating the accountTxs (REST) endpoint as it is not heavily used. This will happen on November 20, 2025 at 4:30 PM UTC

You can use the Block Explorer to fetch account logs. This is the endpoint: https://explorer.elliot.ai/api/accounts/%7BaccountID%7D/logs?pub_data_type=&limit=20&offset=0

We're doing a network upgrade on November 23, 2025 at 12:00 PM UTC. Downtime should be under 15 minutes. Manage your positions in advance, orders will not get placed during downtime.

Added Lighter Explorer API endpoints section in the API reference docs

https://apidocs.lighter.xyz/reference

There are different rate limits that apply to these endpoints: https://apidocs.lighter.xyz/docs/rate-limits#-explorer-rest-api-endpoint-limits