Skip to content
This repository was archived by the owner on Jul 15, 2025. It is now read-only.
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/guides/deploy-warp-route.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,11 @@ hyperlane config create warp
If your config looks correct, you can now skip to [Step 2: Deployment](#2-deployment).
Or see below for details on how to define your config manually.

If you want to use some custom chains in your warp route deployment use the --chains flag
```bash
hyperlane config create warp --chains <PATH-TO-CHAINS-FILE>
```

:::

#### Base
Expand Down Expand Up @@ -90,6 +95,15 @@ Run the following command to initiate the Warp Route deployment:
hyperlane deploy warp
```

:::tip

If you are using some custom chains in your warp route config use the --chains flag while deploying
```bash
hyperlane deploy warp --chains <PATH-TO-CHAINS-FILE>
```

:::

Once finished, the CLI will create two new JSON artifact files: `warp-deployment` and `warp-ui-token-config`. The first contains just addresses for the newly deployed Warp router contracts. The second is a config file for the Warp UI, which you can use for the next optional step.

## 3. Testing
Expand Down