migrating-an-onchainkit-app

Migrate dApps from @coinbase/onchainkit to wagmi and viem.

104|114|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/base/skills --skill migrating-an-onchainkit-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-an-onchainkit-app
Source: https://github.com/base/skills/tree/main/skills/migrating-an-onchainkit-app
Command: npx skills add https://github.com/base/skills --skill migrating-an-onchainkit-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers migrate their decentralized applications from the @coinbase/onchainkit library to a more flexible, standalone setup using wagmi and viem. This reduces dependencies and offers greater control over the application's architecture.

Core Features & Use Cases

  • Provider Migration: Replaces OnchainKitProvider with WagmiProvider and QueryClientProvider.
  • Wallet Component Migration: Replaces OnchainKit wallet UI components with a custom WalletConnect component.
  • Transaction Component Migration: Replaces OnchainKit transaction UI components with a custom TransactionForm component.
  • Use Case: A developer has an existing dApp using OnchainKit for wallet connection and transaction handling. They want to remove the OnchainKit dependency to have more control over the UI and logic. This Skill guides them through replacing each OnchainKit component with its wagmi/viem equivalent.

Quick Start

Migrate my onchainkit app to wagmi.

Frequently Asked Questions about migrating-an-onchainkit-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my dApp from OnchainKit to wagmi and viem?

To migrate from OnchainKit to wagmi and viem, you replace the OnchainKitProvider with WagmiProvider and QueryClientProvider, swap wallet UI components for a custom WalletConnect component, and replace transaction UI elements with a custom TransactionForm component.

What is the process for replacing OnchainKit providers in a web3 application?

Replacing OnchainKit providers involves detecting existing OnchainKitProvider usage and migrating the provider configurations to use WagmiProvider alongside QueryClientProvider, which reduces external dependencies and offers greater architectural control.

Can I replace OnchainKit wallet and transaction components with custom wagmi logic?

Yes, you can replace OnchainKit wallet and transaction UI components by building a custom WalletConnect component for wallet interfaces and a custom TransactionForm component to handle transactions directly using wagmi and viem.

Why should I migrate my frontend from OnchainKit to wagmi and viem?

Migrating from OnchainKit to wagmi and viem reduces your project dependencies and provides greater control over your decentralized application's UI and transaction handling logic by implementing direct wagmi and viem code.

What are the final steps after replacing OnchainKit components with wagmi and viem?

After replacing OnchainKit components with wagmi and viem equivalents, the final steps involve performing a comprehensive cleanup to remove residual OnchainKit dependencies and verifying that the application functions correctly.