# Local chain endpoints

Source: https://docs.settlemint.com/docs/developer-guides/platform-setup/local-dev-chain
Understand the local EVM endpoint names used when connecting DALP services to a local development network.



DALP local environments read HTTP and WebSocket RPC endpoints from `ANVIL_URL` and `ANVIL_WS_URL`. Use these endpoint names for local EVM testing before connecting services to a shared test network or production network.

## Endpoint names [#endpoint-names]

The default platform network key is `local`, with the display name `Local Development`. That local profile reads these endpoint variables:

| Setting        | Default                 | Purpose                                                                                           |
| -------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
| `ANVIL_URL`    | `http://localhost:8545` | HTTP JSON-RPC endpoint used by local services.                                                    |
| `ANVIL_WS_URL` | `ws://localhost:8545`   | WebSocket JSON-RPC endpoint used by local services that need subscriptions or live chain updates. |

Keep these names when you override the local endpoint. The DALP local profile reads these keys even when the endpoint points to another EVM-compatible development node.

## Local state boundary [#local-state-boundary]

Treat local chain state as disposable test state. A local node can preserve state across restarts for development convenience, but that state is not production evidence, an audit record, or a backup of a live network.

Use a shared test network or production network configuration when the workflow depends on durable records, monitored infrastructure, recovery procedures, or evidence for an external audit.

## Related pages [#related-pages]

* [Platform setup overview](/docs/developer-guides/platform-setup/platform-overview) explains the broader setup path before asset creation.
* [Organization deployment API](/docs/developer-guides/platform-setup/organization-deployment-api) covers organization provisioning through the API.
* [Deployment architecture](/docs/architecture/components/asset-contracts/deployment-architecture) explains asset-contract deployment behavior.