# Environments & Chains

> The hosts behind the Proxima API, and the chain and network identifiers used in request paths.

Proxima runs as a set of services. The REST API carries almost every operation; dedicated hosts serve realtime
channels, the market datafeed, images and support tickets.

## Hosts

| Service | Production | Development |
| --- | --- | --- |
| REST API | `https://api-mig.proxima.tools` | `https://api.proximatool.dev` |
| Realtime channels (Centrifugo) | `wss://ws.proxima.tools/connection/websocket` | `wss://ws.proximatool.dev/connection/websocket` |
| Market datafeed | `wss://datafeed.proxima.tools/ws` | `wss://datafeed.proximatool.dev/ws` |
| Datafeed HTTP | `https://datafeed.proxima.tools` | `https://datafeed.proximatool.dev` |
| Image proxy | `https://img.proxima.tools` | Production only |
| Support tickets | `https://support-api.proxima.tools` | Production only |

A second production API, `https://api-prod-update.proxima.tools`, is used to stage releases. It runs alongside
the same production realtime and datafeed hosts. Use it only when Proxima asks you to verify a release.

> **Warning:** Production and development are separate deployments. Accounts, wallets, sessions and launches do not carry over
> from one to the other, so a token issued by one host is rejected by the other.

Every REST path in this reference is relative to the API base URL. Examples use production:

```bash
export PROXIMA_API=https://api-mig.proxima.tools
curl "$PROXIMA_API/health"
```

## Chains

Endpoints that act on a single chain take its identifier in the path, usually as `{chain_id}`. The identifiers
are stable lowercase strings:

| `chain_id` | Chain | `network_type` | Native asset | Base units per native unit | Status |
| --- | --- | --- | --- | --- | --- |
| `sol` | Solana | `svm` | SOL | `1000000000` (10⁹) | Live |
| `eth` | Ethereum | `evm` | ETH | `1000000000000000000` (10¹⁸) | Live |
| `bsc` | BNB Smart Chain | `evm` | BNB | `1000000000000000000` (10¹⁸) | Live |
| `base` | Base | `evm` | ETH | `1000000000000000000` (10¹⁸) | Live |
| `robinhood` | Robinhood | `evm` | ETH | `1000000000000000000` (10¹⁸) | Live |
| `arc` | Arc | `evm` | USDC | `1000000000000000000` (10¹⁸) | Live |
| `xlayer` | X Layer | `evm` | OKB | `1000000000000000000` (10¹⁸) | Live |
| `monad` | Monad | `evm` | MON | `1000000000000000000` (10¹⁸) | Not live |

The table reflects the platform constants at the time of writing. Read
[`GET /get-constants`](/reference/platform/) at startup instead of hard-coding it: the response lists every chain
with its `live` flag, native symbol, known tokens, dust and minimum balance thresholds, the launchpads and DEXs it
supports (`dexs`) and the features enabled on it (`features`).

## Network types

Wallets are created per virtual machine rather than per chain: an EVM wallet holds the same address on Ethereum,
BSC, Base and every other EVM chain. Wallet endpoints therefore take a `{network_type}` path segment:

| `network_type` | Virtual machine | Chains |
| --- | --- | --- |
| `svm` | Solana Virtual Machine | `sol` |
| `evm` | Ethereum Virtual Machine | `eth`, `bsc`, `base`, `robinhood`, `arc`, `xlayer`, `monad` |

Rule of thumb: wallet creation and imports are scoped by `network_type`; anything that sends a transaction, reads a
balance on a specific chain or targets a launchpad is scoped by `chain_id`.

```http
POST /wallets/evm/add            # one EVM wallet, usable on every EVM chain
POST /launch/bsc/import-mint     # import a token that lives on BSC
GET  /sol/shield/get-shield-info # Shield state on Solana
```

## Health check

`GET /health` needs no authentication. Use it to check reachability and to measure clock drift: `ts` is the server
time in epoch milliseconds.

```json
{ "ok": true, "ts": 1767225600000 }
```

The public status page at [status.proxima.tools](https://status.proxima.tools/) reports incidents and maintenance
windows.
