> For the complete documentation index, see [llms.txt](https://varntix.gitbook.io/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://varntix.gitbook.io/resources/deposits-and-withdrawals/supported-currencies.md).

# Supported Currencies

### Which currencies are supported?

Varntix supports a range of widely used stablecoins and cryptocurrencies.

Users can make deposits using the following currencies: Bitcoin, Ethereum, Solana, USDT, USDC 

Available currencies and networks will be displayed within the deposit section of your dashboard before initiating a transfer.

### How long do deposits take?

Deposit times depend on the network used:

• Most crypto deposits are confirmed within minutes\
• During periods of network congestion, processing times may be longer

Your balance will update once the required confirmations are completed.

### Can I deposit at any time?

Yes. Deposits can be made at any time, subject to network availability and platform status.

### Is there a minimum deposit amount?

Yes the minimum amount you can deposit is $20, please note any deposits below this amount will not be credited to your account.

<br>


---

# 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://varntix.gitbook.io/resources/deposits-and-withdrawals/supported-currencies.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.