> ## Documentation Index
> Fetch the complete documentation index at: https://help.primevault.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Chains, Tokens and dApps

## How does PrimeVault add new chains? What is different about EVM and non-EVM?

PrimeVault uses a modular adapter for each chain. EVM chains share the same signing and transaction patterns, so enablement is mostly configuration. Non-EVM chains such as Tron or Solana need a purpose-built adapter. Every new adapter is tested on a testnet, rolled out as a small canary in production, and monitored with rollback ready. Policies and simulations work the same way across adapters.

You can see the integrations supported by us here: [https://primevault.notion.site/primevault-integrations-overview](https://primevault.notion.site/primevault-integrations-overview)

## Can we restrict or allow specific dApps, bridges, or DEX routes?

Yes. You can allow or deny by dApp, category, contract, or function, and set size limits and approval quorums for each route. If you do not use DeFi or bridges, you can disable them entirely in policy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.