> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# spotDeployState | Hyperliquid info
> The info endpoint with type: "spotDeployState" returns the Spot Deploy Auction state. Available on Hyperliquid info via Chainstack.
This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
The `info` endpoint with `type: "spotDeployState"` returns the Spot Deploy Auction state. It exposes per‑token genesis state and the current gas auction parameters used for spot token deployment.
## Parameters
### Request body
* `type` (string, required) — The request type. Must be `"spotDeployState"` to retrieve spot deployment state information.
* `user` (string, required) — Address in 42-character hexadecimal format. Can be zero address (`0x0000000000000000000000000000000000000000`) for global state information.
## Response
The response is an object with two primary sections:
### States
Array of token genesis entries. Each entry includes:
* `token` (integer) — Token ID.
* `spec` (object) — Token spec with:
* `name` (string)
* `szDecimals` (number)
* `weiDecimals` (number)
* `fullName` (string, optional)
* `spots` (array of integers) — Spot pair indices associated with the token.
* `maxSupply` (integer)
* `hyperliquidityGenesisBalance` (string)
* `totalGenesisBalanceWei` (string)
* `userGenesisBalances` (array) — Tuples of `[address, balance]` in string form.
* `existingTokenGenesisBalances` (array) — Tuples of `[tokenIndex, balance]` in string form.
### Gas auction
Current auction parameters:
* `startTimeSeconds` (integer) — Auction start time (seconds since epoch).
* `durationSeconds` (integer) — Auction duration in seconds.
* `startGas` (string) — Starting gas amount.
* `currentGas` (string or null) — Current gas amount.
* `endGas` (string, optional) — Ending gas amount when completed.
### Understanding spot token deployment
**Deployment process:**
* Users submit token deployment requests with specified parameters
* Requests are queued and processed based on system capacity
* Successful deployments create new tradeable spot tokens
* Deployed tokens become available for spot trading
**System parameters:**
* **Deployment cost**: Fee required to deploy new tokens
* **Supply limits**: Minimum and maximum token supply constraints
* **Queue management**: Fair processing of deployment requests
**Token lifecycle:**
* **Request submission**: Users submit deployment parameters
* **Queue processing**: Requests are processed in order
* **Token creation**: Successful deployments create new tokens
* **Trading availability**: Deployed tokens become tradeable
## Example request
```shell Shell theme={"system"}
curl -X POST \
-H "Content-Type: application/json" \
-d '{"type": "spotDeployState", "user": "0x0000000000000000000000000000000000000000"}' \
https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info
```
```python Python (hyperliquid-python-sdk) theme={"system"}
from hyperliquid.info import Info
info = Info("YOUR_CHAINSTACK_ENDPOINT", skip_ws=True)
# Posts {"type": "spotDeployState", "user": user} to /info
state = info.query_spot_deploy_auction_status(
"0x0000000000000000000000000000000000000000"
)
print(state)
```
```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
import { HttpTransport, InfoClient } from "@nktkas/hyperliquid";
const transport = new HttpTransport({ apiUrl: "YOUR_CHAINSTACK_ENDPOINT" });
const info = new InfoClient({ transport });
// Posts {"type": "spotDeployState", "user": user} to the info endpoint
const state = await info.spotDeployState({
user: "0x0000000000000000000000000000000000000000",
});
console.log(state);
```
**Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
## Use case
The `info` endpoint with `type: "spotDeployState"` is useful for:
* **Auction monitoring**: Read current `gasAuction` timing and gas parameters.
* **Genesis state inspection**: Review token `states` and genesis balances.
* **Discovery**: Identify tokens and spot indices associated with upcoming or configured deployments.
This endpoint is particularly valuable for token creators, market participants interested in new token launches, and platforms that need to monitor or facilitate spot token deployments on the Hyperliquid exchange. It provides essential visibility into the token deployment ecosystem and system operational status.
## OpenAPI
````yaml openapi/hyperliquid_node_api/hypercore_info/info_spotdeploystate.json post /4f8d8f4040bdacd1577bff8058438274/info
openapi: 3.0.0
info:
title: Hyperliquid Node API
version: 1.0.0
description: This is an API for interacting with Chainstack Hyperliquid node.
servers:
- url: https://hyperliquid-mainnet.core.chainstack.com
security: []
paths:
/4f8d8f4040bdacd1577bff8058438274/info:
post:
tags:
- hyperliquid operations
summary: info (spotDeployState)
operationId: infoSpotDeployState
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
type:
type: string
default: spotDeployState
enum:
- spotDeployState
description: >-
Request type to retrieve spot token deployment state
information
user:
type: string
default: '0x0000000000000000000000000000000000000000'
description: >-
Address in 42-character hexadecimal format (can be zero
address for global state)
required:
- type
- user
responses:
'200':
description: Spot token deployment state and configuration information
content:
application/json:
schema:
type: object
description: Current state of spot token deployment system
properties:
deploymentEnabled:
type: boolean
description: Whether new spot token deployments are currently enabled
totalDeployments:
type: integer
description: Total number of tokens deployed on the spot system
deploymentCost:
type: string
description: Cost to deploy a new spot token (in USD)
maxSupply:
type: string
description: Maximum token supply allowed for new deployments
minSupply:
type: string
description: Minimum token supply required for new deployments
deploymentQueue:
type: array
description: Queue of pending token deployments
items:
type: object
properties:
deployer:
type: string
description: Address of the token deployer
tokenName:
type: string
description: Name of the token to be deployed
tokenSymbol:
type: string
description: Symbol of the token to be deployed
supply:
type: string
description: Initial supply of the token
queuePosition:
type: integer
description: Position in the deployment queue
estimatedDeployTime:
type: integer
description: Estimated deployment timestamp in milliseconds
recentDeployments:
type: array
description: Recently deployed tokens
items:
type: object
properties:
tokenAddress:
type: string
description: Contract address of the deployed token
tokenName:
type: string
description: Name of the deployed token
tokenSymbol:
type: string
description: Symbol of the deployed token
deployer:
type: string
description: Address of the token deployer
deployTime:
type: integer
description: Deployment timestamp in milliseconds
initialSupply:
type: string
description: Initial supply of the deployed token
systemStatus:
type: string
description: >-
Current status of the deployment system (e.g., 'active',
'maintenance', 'paused')
````