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

# nexus network

**Audience:** Nexus CLI users and integrators.

**Command:** `nexus network`.

**Generated from:** Nexus CLI `v2.1.1` tagged source at commit `08bfe76e726922ce512d623fbc1d2e1bd786bcd4` (generated inventory preserved below).

This page is the complete help tree for `nexus network`. Global output flags can appear after the family or nested subcommand.

```
Manage Nexus network fees

Usage: nexus network [OPTIONS] <COMMAND>

Commands:
  configure-leader-registry Configure the complete leader registry policy
  configure-priority-fee-vault  Configure the priority fee vault exchange rate
  swap-us-for-sui               Swap an owned `$US` coin for SUI from the priority fee vault
  drain-priority-fee-vault-sui  Drain all available SUI from the priority fee vault
  withdraw-priority-fee         Withdraw a leader's `$US` priority fee share
  collect-priority-fees         Collect one leader capability's priority fee deposits
  help                          Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network configure-leader-registry`

This command applies the unbonding delay, minimum `$US` stake, and per-transaction MIST ceiling together. It requires the configured signer to control the leader administration capability. A new registry begins with a fail-closed maximum minimum stake, so configure this policy before registering leaders.

```
Configure the complete leader registry policy

Usage: nexus network configure-leader-registry [OPTIONS] --unbonding-duration-ms <MILLISECONDS> --min-stake-us <AMOUNT> --max-transaction-budget-mist <MIST>

Options:
      --unbonding-duration-ms <MILLISECONDS>     Delay before requested leader stake can be claimed
      --min-stake-us <AMOUNT>                     Minimum leader stake in `$US` atomic units
      --max-transaction-budget-mist <MIST>        Maximum transaction budget available to one leader
  -h, --help                                      Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network configure-priority-fee-vault`

This command resolves `priority_fee_vault_owner_cap` and `us_token` from configured `NexusObjects`. The configured signer must own the cap, and the cap must be bound to the canonical vault. Use `nexus conf get --json` plus cap/vault object readback before configuration; the rate argument alone does not establish custody.

```
Configure the priority fee vault exchange rate

Usage: nexus network configure-priority-fee-vault [OPTIONS] --exchange-rate-million-mists-us <RATE>

Options:
      --exchange-rate-million-mists-us <RATE>  $US atomic units per 1,000,000 MIST
  -h, --help                                   Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network swap-us-for-sui`

The default `--min-sui-out 0` is not a safe slippage policy. No CLI/high-level SDK ordinary quote command exists. Use the [priority-fee vault guide](/guides/tokenomics/use-priority-fee-vault.md) to inspect the observed quote and derive a declared tolerance, then pass the computed nonzero minimum explicitly. Rate/liquidity races below that minimum abort atomically. Use the drain command only for the separate full-SUI-balance behavior.

```
Swap an owned `$US` coin for SUI from the priority fee vault

Usage: nexus network swap-us-for-sui [OPTIONS] --us-coin <OBJECT_ID>

Options:
      --us-coin <OBJECT_ID>  Owned Coin<US> object ID
      --min-sui-out <MIST>   Minimum SUI output accepted [default: 0]
  -h, --help                 Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network drain-priority-fee-vault-sui`

This command consumes the input US coin and returns SUI plus a newly materialized US refund object. Select that refund only from the swap transaction digest's created object changes by exact configured `Coin<US>` type and recipient, require one unique ID, then fetch its owner/version/digest/balance and compare balance with `us_refunded`; use the [priority-fee vault guide](/guides/tokenomics/use-priority-fee-vault.md). Follow it with a fresh vault-state query and require zero SUI before leader withdrawal; see [Priority-Fee Tokenomics](/concepts/13-priority-fee-tokenomics.md).

```
Drain all available SUI from the priority fee vault

Usage: nexus network drain-priority-fee-vault-sui [OPTIONS] --us-coin <OBJECT_ID>

Options:
      --us-coin <OBJECT_ID>  Owned Coin<US> object ID used to buy all available vault SUI
  -h, --help                 Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network withdraw-priority-fee`

`share_to_withdraw` is a leader vault share amount, not immediate Sui transaction gas or a SUI-denominated coin amount. The selected handler withdraws the leader's `$US` priority-fee share. The generated help wording below is retained as shipped CLI text; use transaction effects and vault readback to confirm the resulting `$US` transfer.

```
Withdraw a leader's `$US` priority fee share

Usage: nexus network withdraw-priority-fee [OPTIONS] --leader-cap <OBJECT_ID>

Options:
      --leader-cap <OBJECT_ID>     Leader capability object ID
      --share-to-withdraw <SHARE>  SUI denominated share to withdraw; defaults to the full leader
                                   share
  -h, --help                       Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```

#### `nexus network collect-priority-fees`

The CLI does not expose a separate deposit-list or arbitrary leader-membership query. Follow the documented [priority-fee vault behavior](/concepts/13-priority-fee-tokenomics.md), then compare the command's collected/skipped/unavailable IDs with the after-state. Unavailable IDs may have been consumed concurrently; post-snapshot deposits wait for a later invocation. Skipped removed-leader children are not ordinary retries: the APIs cannot recreate the same leader-cap record, reassign, collect, delete, or refund them.

```
Collect one leader capability's priority fee deposits

Usage: nexus network collect-priority-fees [OPTIONS] --leader-cap-id <OBJECT_ID>

Options:
      --leader-cap-id <OBJECT_ID>  Leader capability whose initially visible deposits will be
                                   collected
      --batch-size <COUNT>         Maximum deposits per transaction [default: 128]
  -h, --help                       Print help

Gas:
  -g, --sui-gas-coin <OBJECT_ID>  Optional owned gas coin object ID. Most commands use address
                                  balance gas when omitted.
  -b, --sui-gas-budget <MIST>     Maximum MIST spent on Sui transaction gas. [default: 100000000]

Output:
      --json        Emit machine readable JSON
  -v, --verbose...  Increase diagnostic detail
  -q, --quiet...    Show errors only
```


---

# 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 dynamically by asking a question.

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

```
GET https://docs.talus.network/reference/cli/network.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 `build a script that syncs our docs to a CMS` 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.
