> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/reference/stacks.js/stacks-network/network/stacksnetwork.md).

# StacksNetwork

The core type representing a Stacks network configuration. Contains chain identifiers, address versioning, magic bytes, and the API client configuration.

***

### Usage

```ts
import { StacksNetwork, STACKS_MAINNET } from '@stacks/network';

// Use a pre-configured network
const network: StacksNetwork = STACKS_MAINNET;

// Or create a custom network with a different API URL
const customNetwork: StacksNetwork = {
  ...STACKS_MAINNET,
  client: { baseUrl: 'https://my-custom-api.example.com' },
};
```

#### Notes

* In most cases, you can pass a string (`'mainnet'`, `'testnet'`, `'devnet'`, `'mocknet'`) instead of a full `StacksNetwork` object to `@stacks/transactions` functions.
* Use the `StacksNetwork` type directly when you need a custom API URL, a custom fetch function, or want to inspect network properties.
* The `client.fetch` property is optional — if not provided, a default fetch function is created automatically by the networking helpers.

[**Reference Link**](https://github.com/stx-labs/stacks.js/tree/main/packages/network/src/network.ts#L14)

***

### Definition

```ts
type StacksNetwork = {
  chainId: number;
  transactionVersion: number;
  peerNetworkId: number;
  magicBytes: string;
  bootAddress: string;
  addressVersion: {
    singleSig: number;
    multiSig: number;
  };
  client: {
    baseUrl: string;
    fetch?: FetchFn;
  };
};
```

***

### Properties

| Property                   | Type                   | Description                                                                                  |
| -------------------------- | ---------------------- | -------------------------------------------------------------------------------------------- |
| `chainId`                  | `number`               | The chain ID used for replay protection. `0x00000001` for mainnet, `0x80000000` for testnet. |
| `transactionVersion`       | `number`               | Transaction version byte. `0x00` for mainnet, `0x80` for testnet.                            |
| `peerNetworkId`            | `number`               | Peer network ID for P2P broadcasting.                                                        |
| `magicBytes`               | `string`               | Two-character magic bytes identifying the network (`X2`, `T2`, `id`).                        |
| `bootAddress`              | `string`               | The boot contract address for the network.                                                   |
| `addressVersion.singleSig` | `number`               | Address version byte for single-sig addresses.                                               |
| `addressVersion.multiSig`  | `number`               | Address version byte for multi-sig addresses.                                                |
| `client.baseUrl`           | `string`               | The base URL for the Stacks API node.                                                        |
| `client.fetch`             | `FetchFn \| undefined` | Optional custom fetch function. Created automatically if not provided.                       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/reference/stacks.js/stacks-network/network/stacksnetwork.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.