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

# CLI Reference

## Transaction

### LiquidStake

Liquid stake coin.

It requires `whitelisted_validators` to be registered. The [config.yml](https://github.com/crescent-network/crescent/blob/main/config.yml) file registers a single whitelist validator for testing purpose.

#### Usage

```
liquid-stake [amount]
```

| **Argument** | **Description**                                           |
| ------------ | --------------------------------------------------------- |
| amount       | amount of coin to liquid stake; it must be the bond denom |

#### Example

```
crescentd tx liquidstaking liquid-stake 5000000000stake \
--chain-id localnet \
--from bob \
--keyring-backend test \
--gas 1000000 \
--broadcast-mode block \
--yes \
--output json | jq

#
# Tips
#
# Query account balances
# Notice the newly minted bToken
crescentd q bank balances cre1mzgucqnfr2l8cj5apvdpllhzt4zeuh2c5l33n3 -o json | jq

# Query the voter's liquid staking voting power
crescentd q liquidstaking voting-power cre1mzgucqnfr2l8cj5apvdpllhzt4zeuh2c5l33n3 -o json | jq
```

### LiquidUnstake

Unstake coin.

#### Usage

```
liquid-unstake [amount]
```

| **Argument** | **Description**                                        |
| ------------ | ------------------------------------------------------ |
| amount       | amount of coin to unstake; it must be the bToken denom |

#### Example

```
crescentd tx liquidstaking liquid-unstake 1000000000bstake \
--chain-id localnet \
--from bob \
--keyring-backend test \
--gas 1000000 \
--broadcast-mode block \
--yes \
--output json | jq

#
# Tips
#
# Query account balances
# Notice the newly minted bToken
crescentd q bank balances cre1mzgucqnfr2l8cj5apvdpllhzt4zeuh2c5l33n3 -o json | jq

# Query the voter's liquid staking voting power
crescentd q liquidstaking voting-power cre1mzgucqnfr2l8cj5apvdpllhzt4zeuh2c5l33n3 -o json | jq
```

## Query

### Params

Query the current liquidstaking parameters information.

#### Usage

```
params
```

#### Example

```
crescentd query liquidstaking params -o json | jq
```

### LiquidValidators

Query all liquid validators.

#### Usage

```
liquid-validators
```

#### Example

```
crescentd query liquidstaking liquid-validators -o json | jq
```

### States

Query net amount state.

#### Usage

```
states
```

#### Example

```
crescentd query liquidstaking states -o json | jq
```

### VotingPower

Query the voter’s staking and liquid staking voting power.

#### Usage

```
voting-power [voter]
```

| **Argument** | **Description**       |
| ------------ | --------------------- |
| voter        | voter account address |

#### Example

```
crescentd query liquidstaking voting-power cre1mzgucqnfr2l8cj5apvdpllhzt4zeuh2c5l33n3 -o json | jq
```


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crescent.network/developer-guide/cli-and-api/liquidstaking-module/cli-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
