Skip to content
The Konekt mark

konekt

A better WalletConnect client for performance-minded apps. A Vite React app first-loads 11.03 kB with Konekt, against 145.74 kB for the official provider and 721.26 kB with AppKit.

Konekt gives your app an EIP-1193-compatible provider backed by WalletConnect v2. It has no @walletconnect runtime dependency, and chain support is split into optional imports so unused code can stay out of your bundle.

Measured in a real app

A Vite React app first-loads 11.03 kB with Konekt, 145.74 kB with the official Ethereum Provider, and 721.26 kB with AppKit. React is marked external in all three.

No runtime framework tax

Konekt has no @walletconnect runtime dependency. Add chain adapters, reads, authentication, and UI only when your app uses them.

Your stack stays in charge

Keep viem, wagmi, ethers, your RPCs, and your design system. Konekt owns WalletConnect sessions and requests—not the rest of your application.

Start with one provider

Call Provider.init() once, show the pairing QR, and wait for the user to approve the connection in their wallet.

Choose your networks

Add EVM, Solana, Bitcoin, or Cosmos networks. Konekt proposes only the networks and wallet methods you configure.

Bring your own UI—or use ours

Listen for a pairing URI and render it yourself, or install konekt-ui for a React wallet picker and QR modal.

Add sign-in when you need it

The optional SIWE feature requests authentication during pairing. Verify the signed result on your server.

The guides are a path, from the easiest setup to full control. Take them in order:

  1. Getting started — a React app with a connect button, using konekt, konekt-ui, and wagmi.
  2. Design your own connect UI — your own buttons and dialogs on top of the pairing hooks.
  3. Plain JavaScript — the provider itself, with no framework and no UI package.
  4. Solana, Cosmos, Bitcoin, and Sui — the same provider beyond Ethereum.
  5. Everything together — one connection covering several ecosystems at once.

Or jump straight to what you need:

Start with the integration instructions, then use /llms.txt for an index or /llms-full.txt for the complete guides.

llms.txtllms-full.txt