Create account
Home › Features › WalletConnect
Features · dApps under governance

Your vault inside EVM dApps — under policy

DeFi access without exporting a key anywhere

Connect a vault to any EVM dApp through WalletConnect: the dApp sees a wallet, your team sees a governed vault. Message signing, typed-data signing and transactions all route through the same policies and the same MPC ceremony as everything else.

Share the Trust, Guard the Keys

Create accountLive on testnet in an afternoon
Compare PlansIncluded in a plan, not an add-on
The problem

A browser extension is the wrong place for corporate funds

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 session is initiated by your team, and every request the dApp makes still travels the full approval and signing path.

  • The vault, not a side walletFunds stay where your policy applies. There is no separate operational wallet to fund, watch and reconcile.
  • Every request is governedMessage signing and transactions from a dApp session clear the same rules as any other request.
  • Sessions are revocableA pairing is visible and can be ended; nothing about a dApp connection is permanent.

How it works

A governed wallet, not a browser extension

Sessions are created and terminated from the dashboard, permission-gated per role. A dApp transaction is a transaction — it clears your rules and signs in the normal 3-of-3 ceremony, or it does not sign at all.

  • ✓personal_sign, typed data (EIP-712) and transactions — EVM dApps
  • ✓Sessions visible and revocable centrally
  • ✓Every dApp action lands in the audit trail
walletconnect session — dApp
U
Uniswap
session active · ops vault
connected
S
Swap request
1.5 ETH → USDC
policy check
M
MPC ceremony
3-of-3 signature
signed
Specification

Pairing specification

Including the limitation a competitor's page would leave out.

ProtocolWalletConnect session initiated from the dashboard by pairing with the dApp.
Vault typeAvailable on legacy vault types today. Modern v2 vaults cannot pair yet — confirm with us before you plan a DeFi workflow around it.
GovernancedApp-originated transactions and message signatures follow the normal approval rules and the normal MPC ceremony.
CoverageEVM dApps.
EvidenceSession activity lands in the same transaction history as everything else.
No safety layerThere is no transaction simulation and no destination allow-list between a dApp and your policy — approvals are the control.
RevocationEnd a session from the dashboard at any time.
RoadmapSupport on modern vaults is planned; we would rather flag the gap than let you discover it mid-integration.

Frequently asked questions

Get answers to commonly asked questions.

Which chains?

EVM chains — that is where WalletConnect delivers real coverage today, and we would rather state that than advertise namespaces that do not work.

Can any team member connect a dApp?

Only roles holding the WalletConnect permission; sessions are centrally visible and revocable.

Which plans?

All of them.

Share the Trust Guard the Keys

The dApp gets a wallet; you keep the governance.

Create accountRequest Demo