Skip to main contentFor advanced integrations, LaunchBlitz exposes a WebSocket connection for transaction execution.
Overview
The transaction socket handles:
- Token creation transactions
- Buy/sell orders
- Transaction confirmation and status updates
Connection
The default endpoint is:
This can be configured in Profile → Preferences → Advanced Settings → TX Executor.
Authentication
Connections require a valid session. The socket authenticates using your LaunchBlitz session token.
The socket uses a ping/pong heartbeat system with automatic reconnection.
Events
| Event | Direction | Description |
|---|
ping | Client → Server | Heartbeat check |
pong | Server → Client | Heartbeat response |
tx_request | Client → Server | Submit transaction |
tx_status | Server → Client | Transaction update |
tx_confirmed | Server → Client | Transaction confirmed |
tx_failed | Server → Client | Transaction failed |
Transaction Flow
- Request — Client sends transaction details
- Processing — Server builds and submits transaction
- Status — Server sends status updates
- Confirmation — Final confirmation with signature
Audio Notifications
You can enable audio notifications for transaction confirmations:
- Configure in Preferences → Audio Settings
- Different sounds for success/failure
Status Codes
| Code | Meaning |
|---|
pending | Transaction submitted |
processing | Being processed |
confirmed | Successfully confirmed |
failed | Transaction failed |
Reconnection
The socket automatically reconnects on disconnect:
- Exponential backoff
- Session re-authentication
- State recovery
Local Development
For testing, you can run a local executor:
Set this in TX Executor preferences.