# WalletConnect

Your vault inside EVM dApps, under policy — DeFi access without exporting a key anywhere.

DeFi access usually means a hot wallet in someone's browser, outside every control you built.
WalletConnect pairing lets a governed vault connect to a dApp instead: the dApp sees a wallet,
your team sees a governed vault, and every request the dApp makes still travels the full approval
and signing path.

## A governed wallet, not a browser extension

- **The vault, not a side wallet** — funds stay where your policy applies, so there is no separate
  operational wallet to fund, watch and reconcile.
- **Every request is governed** — message signing, typed data (EIP-712) and transactions all clear
  the same rules and sign in the normal MPC ceremony, or they do not sign at all.
- **Sessions are revocable** — pairings are created and terminated from the dashboard, visible
  centrally, and permission-gated per role.
- **Every dApp action lands in the audit trail.**

## FAQ

**Which chains does it cover?**
EVM chains, which is where WalletConnect delivers real coverage today. We would rather state that
than advertise namespaces that do not work.

**Who can open a session?**
Only roles holding the WalletConnect permission; sessions are centrally visible and revocable.

## Related

- [Policy Engine](/features/policy-engine)
- [Roles & Permissions](/features/roles-and-permissions)
- [Integrations: DeFi Connectivity](/integrations/defi-connectivity)
- [Unified EVM Address](/features/unified-evm-address)