Some updates

- REST: orderBookOrders endpoint is back up (link below)
- WS: Position funding details from sub messages have been removed

https://apibetadocs.lighter.xyz/reference/orderbookorders

Leverage updates:
$AI16Z: 3x -> 5x
$kFLOKI: 3x -> 5x
$TAO: 3x -> 5x

Also, we’re updating transfer transactions to require an Ethereum wallet signature. This will be for Fast Withdrawals and Internal Transfers. An SDK upgrade with the new flow is coming soon, too.

We’re doing a quick network upgrade today at 8:30PM UTC. Downtime will be under 10 minutes.

Please note: We’ve introduced a new requirement — users must now sign with their wallet for internal transfers and fast withdrawals. This is currently only available on the frontend. SDK support will come with its next upgrade.

FYI — We will be restarting testnet in 10 mins.

Change for account_api endpoint. We are not returning pool info for non pool accounts anymore (PublicPoolInfo)

Please pip install git+https://github.com/elliottech/lighter-python@main to use the endpoint in its new version.

We're doing a quick network upgrade today at 8:30PM UTC. Downtime should be under 15 minutes.

After the upgrade is done, please expect the following:

limit orders will now use order margin, checked at creation as size × price ÷ leverage
- opposite-side limit orders won’t affect each other
- same-side positions will decrease available order margin
- opposite-side positions will increase available order margin
- liquidation engine will work the same as before

Heads up: Transaction rate limits increased from 2400 req/min to 4000 req/min for Premium Accounts

Re: Active orders
We've brought back this endpoint: /accountActiveOrders. You can also fetch via Web Socket.

https://apibetadocs.lighter.xyz/reference/accountactiveorders
https://github.com/elliottech/lighter-python/blob/main/lighter/api/order_api.py#L49

We're doing a quick network upgrade today at 8:30PM UTC. Downtime should be under 10 minutes.

We are seeing limit orders are getting rejected given the order margin changes we've made. If there is any assistance needed, please let us know.

For context, these are the changes: https://t.me/c/2654829739/13

gm, some updates

1 - The /api/v1/publicPools endpoint will be removed on Monday, Aug 25th at 9PM UTC

For static pool information, use /api/v1/publicPoolsMetadata instead:

# Get basic pool catalog with current APY
GET /api/v1/publicPoolsMetadata?limit=50

For account-specific pool data:

# Get your pool shares and basic pool info
GET /api/v1/account?by=index&value=123
# Returns: pool_info and public_pool_shares for that account

For real-time pool updates via WebSocket, use streams/pool_info and streams/account_all_positions.

2 - Send Batch Tx via WS now available: https://apibetadocs.lighter.xyz/docs/websocket-reference#send-batch-tx

gm, these are new examples for sendtx and sendbatchtx for WS — they are in the docs as well:

WS SendTx: https://github.com/elliottech/lighter-python/blob/main/examples/ws_send_tx.py
WS SendBatchTx: https://github.com/elliottech/lighter-python/blob/main/examples/ws_send_batch_tx.py

gm, some updates:

- We're removing the /api/v1/pendingTxs endpoint.
- We're removing nonce field from /api/v1/apikeys.

gm

- Add ID param to WS send_Tx for transaction tracking. Example here: https://github.com/elliottech/lighter-python/pull/46/files

gm

We're doing a quick network upgrade on September 16 at 8:30 PM UTC. Downtime should be under 15 minutes.

Premium Accounts: Volume Quota Updates

- Previously: 10 USDC volume = +1 transaction quota
- Now: 1 USDC volume = +1 transaction quota

- Also, every new premium account starts off with 1000 volume quota

We're doing a quick network upgrade on 26 September 2025 at 20:30 UTC. Expect brief performance degradation lasting less than 5 minutes.

We're doing a quick network upgrade on 29 September 2025 at 20:30 UTC. Downtime should be under 20 minutes.

gm

We're doing a quick network upgrade on October 1 at 12:00 UTC. Downtime should be under 5 minutes.

gm

While scaling our infrastructure, some users experienced order execution delays. We’ve pushed a fix and will roll out further improvements in this week’s network update.