Use WalletConnect

Ekubo Wallet accepts WalletConnect pairing URIs copied from a dapp’s connect-wallet dialog.

1. In the dapp, choose WalletConnect and copy its wc: pairing URI.
2. Open WalletConnect in Ekubo Wallet and paste the URI.
3. Review the dapp identity and requested networks, then choose the account to expose.
4. Approve or reject later requests that your signing policy does not decide automatically.

The wallet validates the pairing before connecting. An arriving proposal raises the wallet window and a notification naming the dapp, because a pairing is as much a decision as any other request. Multiple dapps can be connected at the same time, and each live session can be disconnected from the WalletConnect screen.

Account and chain requests, message signing, typed data, transactions, and supported batched-call requests use the same wallet authority as local requests. Personal messages and typed data always enter native review. Transactions are evaluated by the account’s signing policy: a matching allow rule can sign and submit without another prompt, a review rule or no match opens native review, and a deny rule rejects the request.

Policies are not scoped to a dapp or WalletConnect session. A rule written for an agent or automation also applies when a connected dapp requests the same matching transaction. A connected dapp cannot approve its own request, ask to weaken review, or change policy.

Session lifetime

WalletConnect pairings and session keys remain in memory. They do not persist or reconnect after Ekubo Wallet restarts. Explicitly quitting the wallet or installing an update disconnects every live session.

The pairing URI is a secret while it is usable. Copy it only from the dapp you intend to connect, and do not paste a pairing URI into a chat or agent prompt.