evm-wallet-integration
Skill8 starsChanged 2 months agoApache-2.0View on GitHub
Integrate wallets into Celo dApps. Covers RainbowKit, Dynamic, and wallet connection patterns.
- Reads credentials
- Installs packages
In this repository15 other files it gives its agents.
- 8004Skill
- bridgingSkill
- celo-composerSkill
- celo-defiSkill
- celo-rpcSkill
- celo-stablecoinsSkill
- contract-verificationSkill
- evm-foundrySkill
- evm-hardhatSkill
- fee-abstractionSkill
- minipay-integrationSkill
- thirdwebSkill
- viemSkill
- wagmiSkill
- x402Skill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Create a new project
- Distinctive: line 278
Create a new project (select "AppKit" type)
- Distinctive: line 280
Add to environment variables:
- Distinctive: line 290
Support Multiple Wallets: - Don't force users into one wallet
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
EVM Wallet Integration for Celo
This skill covers integrating wallet connection libraries into Celo dApps.
When to Use
- Adding wallet connection to a dApp
- Supporting multiple wallet types
- Implementing authentication flows
- Building wallet experiences
Wallet Connection Libraries
| Library | Description | Best For |
| Reown AppKit | Official WalletConnect SDK with wagmi | Production React apps |
| Dynamic | Auth-focused with dashboard | Apps needing user management |
| ConnectKit | Simple wagmi integration | Quick setup |
| Custom wagmi | Direct connector setup | Full control |
Reown AppKit
Official WalletConnect SDK for React apps with built-in wallet UI. Supports 600+ wallets.
Source: https://docs.reown.com/appkit
Note: Reown is the company formerly known as WalletConnect Inc. (rebranded in 2024). The protocol and npm packages for wagmi connectors still use "walletConnect" naming.
Installation
npm install @reown/appkit @reown/appkit-adapter-wagmi wagmi viem @tanstack/react-queryGet Project ID
- Go to cloud.reown.com
- Create a new project
- Copy the project ID
Configuration
// config.ts
import { WagmiAdapter } from "@reown/appkit-adapter-wagmi";
import { celo, celoSepolia } from "@reown/appkit/networks";
const projectId = process.env.NEXT_PUBLIC_REOWN_PROJECT_ID!;
export const wagmiAdapter = new WagmiAdapter({
networks: [celo, celoSepolia],
projectId,
ssr: true,
});
export const config = wagmiAdapter.wagmiConfig;Provider Setup
"use client";
import { WagmiProvider } from "wagmi";
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
import { createAppKit } from "@reown/appkit/react";
import { wagmiAdapter } from "./config";
import { celo, celoSepolia } from "@reown/appkit/networks";
const queryClient = new QueryClient();
createAppKit({
adapters: [wagmiAdapter],
networks: [celo, celoSepolia],
projectId: process.env.NEXT_PUBLIC_REOWN_PROJECT_ID!,
metadata: {
name: "My Celo App",
description: "Celo dApp",
url: "https://myapp.com",
icons: ["https://myapp.com/icon.png"],
},
});
export function Providers({ children }: { children: React.ReactNode }) {
return (
<WagmiProvider config={wagmiAdapter.wagmiConfig}>
<QueryClientProvider client={queryClient}>
{children}
</QueryClientProvider>
</WagmiProvider>
);
}Connect Button
import { AppKitButton } from "@reown/appkit/react";
function Header() {
return (
<nav>
<AppKitButton />
</nav>
);
}Custom Connect Button
import { useAppKit, useAppKitAccount } from "@reown/appkit/react";
function WalletConnect() {
const { open } = useAppKit();
const { address, isConnected } = useAppKitAccount();
if (isConnected) {
return (
<div>
<p>Connected: {address}</p>
<button onClick={() => open({ view: "Account" })}>Account</button>
</div>
);
}
return <button onClick={() => open()}>Connect Wallet</button>;
}Using Wagmi Hooks with AppKit
import { useAccount, useBalance, useDisconnect } from "wagmi";
function AccountInfo() {
const { address, isConnected } = useAccount();
const { data: balance } = useBalance({ address });
const { disconnect } = useDisconnect();
if (!isConnected) return null;
return (
<div>
<p>Address: {address}</p>
<p>Balance: {balance?.formatted} {balance?.symbol}</p>
<button onClick={() => disconnect()}>Disconnect</button>
</div>
);
}Dynamic
Authentication-focused wallet connection with user management dashboard.
Source: https://docs.dynamic.xyz
Installation
npm install @dynamic-labs/sdk-reactSetup
import {
DynamicContextProvider,
DynamicWidget,
} from "@dynamic-labs/sdk-react";
function App() {
return (
<DynamicContextProvider
settings={{
environmentId: process.env.NEXT_PUBLIC_DYNAMIC_ENV_ID!,
}}
>
<DynamicWidget />
</DynamicContextProvider>
);
}Enable Celo
- Go to app.dynamic.xyz dashboard
- Navigate to Configurations
- Select EVM card
- Toggle Celo on
Custom Implementation
Build wallet connection without a library using wagmi directly.
Wagmi Configuration
import { http, createConfig } from "wagmi";
import { celo, celoSepolia } from "wagmi/chains";
import { injected, walletConnect, metaMask } from "wagmi/connectors";
const projectId = process.env.NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID!;
export const config = createConfig({
chains: [celo, celoSepolia],
connectors: [
injected(),
walletConnect({ projectId }),
metaMask(),
],
transports: {
[celo.id]: http(),
[celoSepolia.id]: http(),
},
});Wallet Connect Component
import { useConnect, useConnectors, useAccount, useDisconnect } from "wagmi";
function WalletConnect() {
const { connect } = useConnect();
const connectors = useConnectors();
const { address, isConnected } = useAccount();
const { disconnect } = useDisconnect();
if (isConnected) {
return (
<div>
<p>Connected: {address}</p>
<button onClick={() => disconnect()}>Disconnect</button>
</div>
);
}
return (
<div>
{connectors.map((connector) => (
<button
key={connector.uid}
onClick={() => connect({ connector })}
>
{connector.name}
</button>
))}
</div>
);
}Network Configuration
Celo Networks
| Network | Chain ID | Reown Import | Wagmi Import |
| Mainnet | 42220 | celo from @reown/appkit/networks | celo from wagmi/chains |
| Celo Sepolia | 11142220 | celoSepolia from @reown/appkit/networks | celoSepolia from wagmi/chains |
| Celo Sepolia | 11142220 | - | celoSepolia from wagmi/chains |
Reown Project ID
Required for WalletConnect connections. WalletConnect Inc. rebranded to Reown in 2024.
- Go to cloud.reown.com (formerly WalletConnect Cloud)
- Create a new project (select "AppKit" type)
- Copy the project ID
- Add to environment variables:
NEXT_PUBLIC_REOWN_PROJECT_ID=your_project_idNote: The wagmi
walletConnectconnector still uses the same project ID. Only the cloud console was rebranded.
Best Practices
- Support Multiple Wallets - Don't force users into one wallet
- Handle Network Switching - Prompt users to switch to Celo
- Show Connection State - Clear UI for connected/disconnected
- Handle Errors - User-friendly error messages
- Test on Mobile - Mobile browsers and wallet apps
Dependencies
Reown AppKit
{
"dependencies": {
"@reown/appkit": "^1.0.0",
"@reown/appkit-adapter-wagmi": "^1.0.0",
"wagmi": "^2.0.0",
"viem": "^2.0.0",
"@tanstack/react-query": "^5.0.0"
}
}Custom wagmi (without AppKit)
{
"dependencies": {
"wagmi": "^2.0.0",
"viem": "^2.0.0",
"@tanstack/react-query": "^5.0.0"
}
}Additional Resources
- wallet-connectors.md - Connector configuration reference
Source of truth: Celopedia
These skills are focused, task-level references. For anything broader — verified contract addresses, ecosystem and protocol data, listing requirements, grants, governance, migration guides, or cross-cutting Celo questions — Celopedia is the canonical source and is kept current. Where this skill and Celopedia disagree, Celopedia wins.
npx skills add celo-org/celopedia-skillsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

