Institutional-grade connectivity, upgraded UX, and multichain expansion of WalletConnect
Wallet connectivity is the control layer between operators and the applications they interact with. If that layer is unclear, unreliable, or fragmented, everything downstream suffers. Today, we are rolling out a major upgrade to WalletConnect inside Dfns. This release modernizes our integration, improves operator experience, and aligns us with the standards of the WalletConnect Institutional Certified Program. It is both an architectural shift and a user experience refinement.
New Wallet SDK, certification, security, and reliability
The WalletConnect SDK we previously relied on is being deprecated. As part of this upgrade, we are migrating to the Wallet SDK that supports the next generation of WalletConnect integrations. The Wallet SDK enables stronger verification flows, improved session handling, clearer approval prompts, and long-term compatibility with the WalletConnect roadmap. This migration also allows us to align with WalletConnect’s Institutional Certification, a trust framework defining baseline requirements for secure, reliable, and interoperable wallet connections.
At the connection stage, operators now see exactly who they are connecting to. The app’s name and domain are made explicit, and verification status is surfaced via WalletConnect’s Verify API. The requested network and permissions are clearly displayed before any approval takes place. Sessions are not opaque or permanent. They can be revoked directly from the dashboard, and revocation propagates quickly and consistently.
Authentication has also been streamlined. Instead of forcing users through a multi-step flow where they connect, approve, and then separately sign to log in, we are implementing Sign-In with Ethereum (SIWE). SIWE combines connection and authentication into a single prompt so the operator connects and signs once, intentionally. Result: less friction, fewer context switches and a more coherent login experience.
Inside an active session, every request is made explicit. Operators see the app identity, its verification status, the network involved, and the account being used. Transaction approvals clearly display the destination address, the asset, and the amount. If a transaction falls under a policy approval flow, the interface clearly shows it making governance state visible rather than implied.
Security signals are surfaced proactively. If an app’s identity does not match its metadata, or if the Verify API flags a potential risk, operators are warned before they approve. In such cases, proceeding requires deliberate intent rather than a casual confirmation. In other words, WalletConnect interactions are now governed by Dfns’ broader policy and risk model.
Last but not least, reliability has been tightened. Approvals and rejections propagate back to applications within seconds, and session termination immediately removes access. There are no ambiguous states and no lingering permissions. Institutional workflows demand determinism, and this upgrade delivers it.
Multichain expansion and persistent sessions
Until now, our WalletConnect implementation primarily focused on Ethereum and EVM-compatible networks. With this upgrade, we are expanding support to Solana, Tron, and Bitcoin applications (and more soon). Operators can now use the same Dfns wallet infrastructure to connect to multichain dApps while preserving the same governance policies, approval flows, and security guarantees. Multichain does not mean fragmented tooling as the wallet remains one system, regardless of the underlying chain.
We are also introducing persistent pairings and sessions. Operators can close the WalletConnect modal, navigate away, and return later without losing active connections. For teams managing multiple dApps and workflows in parallel, this persistence is essential. WalletConnect becomes a durable part of the Dfns control plane rather than a temporary popup.
This upgrade represents more than a UX refresh, it strengthens the connective layer between governed assets and onchain applications by combining modern SDK infrastructure, institutional verification standards, transparent approval flows, deterministic session handling, and expanded network support. Wallet connectivity should be explicit, secure, and predictable. With this release, it is.
What the dashboard demo: youtu.be/UwZ6DuWyw5M
Build on Dfns today: app.dfns.io/login
