> This page is for Taurus PROTECT, version v3.52.
> For other versions, use one of these documentation indexes:
> - v3.58 (default): https://taurushq.ferndocs.com/protect-capital/v3.58/llms.txt
> - v3.56: https://taurushq.ferndocs.com/protect-capital/v3.56/llms.txt
> - v3.54: https://taurushq.ferndocs.com/protect-capital/v3.54/llms.txt
> - v3.52: https://taurushq.ferndocs.com/protect-capital/v3.52/llms.txt
> - v3.50: https://taurushq.ferndocs.com/protect-capital/v3.50/llms.txt
> - v3.48: https://taurushq.ferndocs.com/protect-capital/v3.48/llms.txt
> - v3.46: https://taurushq.ferndocs.com/protect-capital/v3.46/llms.txt
> - v3.44: https://taurushq.ferndocs.com/protect-capital/v3.44/llms.txt
> - v3.42: https://taurushq.ferndocs.com/protect-capital/v3.42/llms.txt
> - v3.40: https://taurushq.ferndocs.com/protect-capital/v3.40/llms.txt
> - v3.38: https://taurushq.ferndocs.com/protect-capital/v3.38/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://taurushq.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://taurushq.ferndocs.com/_mcp/server.

# Solana

> **Note**
>
> **In this article**
>
> This guide will walk you through how to mint and burn tokens via Taurus CAPITAL APIs. Note that minting EVM based tokens such as ERC 20 tokens is covered in the following article under Smart Contract Mint & Burn.
>
> There are several prerequisite steps that must be taken prior to minting and burning tokens.
>
> 1. You must have a deployed digital asset managed by Taurus CAPITAL.
> 2. The contract instance must be whitelisted (required to import the asset into CAPITAL)
> 3. You must have transaction governance defined for the Asset (required to import the asset into CAPITAL).
> 4. You must have contract interaction governance rules that enable `mint` and `burn` actions on the relevant blockchain.
> 5. You must have a price for the token (at least one active rate from default PROTECT currency to the respective token).

> **Warning**
>
> **Warning**
>
> If any of the above are missing, mint/burn endpoints will not error. The request will be created and then the mint or burn operation will fail.

## Supported Native Tokens

There are separate mint and burn endpoints depending on the token's respective blockchain. Both mint and burn operations follow Taurus' request flow and as such, each call results in the creation of a request which will then need to be approved per the' governance rules in place (see prerequisites above).

We currently support native tokens for Solana and will be adding support for additional tokens in the future.

### Solana Tokens

#### Relative endpoints

* [Mint](/protect-capital/v3.52/reference/requests-sol/create-outgoing-sol-token-mint-request)
* [Burn](/protect-capital/v3.52/reference/requests-sol/create-outgoing-sol-token-burn-request)

#### Step by step instructions:

1. Retrieve the `addressId` of the address authorized to mint. This is the token owner. (you can use the [List Addresses endpoint](/protect-capital/v3.52/reference/addresses/list)for this.
2. Retrieve the `addressId` for the address you where minted tokens should go.
3. Determine the amount in the smallest units of the token. For example, for a token with 4 decimals, 1 token would be represented by 1000.
4. Call the[Create a SOL token mint request](/protect-capital/v3.52/reference/requests-sol/create-outgoing-sol-token-mint-request) endpoint.

Similarly, a burn request can be made by calling the [Create a SOL token burn request](/protect-capital/v3.52/reference/requests-sol/create-outgoing-sol-token-burn-request)endpoint. This endpoint accepts a `fromAddressId` which similarly to mint operations, must be the owner of the token.

\


### Future tokens

In the future as Taurus expands, additional native tokens will be supported and guides will be displayed on this page.