> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/app-guide/defi/solana.md).

# Solana DeFi in Vultisig

Solana in Vultisig DeFi: native staking and Kamino Earn. Deposit, withdraw, and claim from the DeFi tab.

Solana staking and Kamino Earn are on the **DeFi tab**, not Wallet → Functions.

***

## Native staking

Stake SOL to validators through the Solana Stake program.

1. Open **DeFi tab** → **Solana**
2. Choose stake / deactivate / withdraw as offered
3. Enter the amount
4. Sign with your devices

Unstake (deactivate) and withdraw follow Solana's cooldown. The app shows the action that is available on the position.

***

## Kamino Earn

Kamino Earn is a Solana yield vault. The wallet can show a Kamino banner when the vault holds SOL.

1. Open **DeFi tab** → **Solana** (or the Kamino banner on the vault home)
2. Deposit the supported token
3. Withdraw when you want the position back
4. Sign each action with your devices

APY and deposited amounts come from Kamino. Read the position screen before you sign.

***

## Related

* [DeFi overview](/app-guide/defi.md)
* [Swap](/app-guide/wallet/swapping.md) (Jupiter routes Solana swaps)


---

# 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.vultisig.com/app-guide/defi/solana.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.