base/running-a-base-node
skills/running-a-base-node/SKILL.md
Runs a Base node for production environments. Covers hardware requirements, Reth client setup, networking, and sync troubleshooting. Use when setting up self-hosted RPC infrastructure or running archive nodes. Covers phrases like "run a Base node", "set up Base RPC", "Base node hardware requirements", "Reth Base setup", "sync Base node", "self-host Base", or "run my own node".
$ install --global
skillsauthnpx skillsauth add base/base-skills running-a-base-nodeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 3:25 AM139.1s1 file scanned
SKILL.md
- name:
- running-a-base-node
- description:
- Runs a Base node for production environments. Covers hardware requirements, Reth client setup, networking, and sync troubleshooting. Use when setting up self-hosted RPC infrastructure or running archive nodes. Covers phrases like "run a Base node", "set up Base RPC", "Base node hardware requirements", "Reth Base setup", "sync Base node", "self-host Base", or "run my own node".
Running a Base Node
For production apps requiring reliable, unlimited RPC access.
Security
- Restrict RPC access — bind to
127.0.0.1or a private interface, never expose RPC ports (8545/8546) to the public internet without authentication - Firewall rules — only open ports 9222 (Discovery v5) and 30303 (P2P) to the public; block all other inbound traffic
- Run as a non-root user with minimal filesystem permissions
- Use TLS termination (reverse proxy with nginx/caddy) if exposing the RPC endpoint to remote clients
- Monitor for unauthorized access — log and alert on unexpected RPC calls or connection spikes
Hardware Requirements
- CPU: 8-Core minimum
- RAM: 16 GB minimum
- Storage: NVMe SSD, formula:
(2 × chain_size) + snapshot_size + 20% buffer
Networking
Required Ports:
- Port 9222: Critical for Reth Discovery v5
- Port 30303: P2P Discovery & RLPx
If these ports are blocked, the node will have difficulty finding peers and syncing.
Client Selection
Use Reth for Base nodes. Geth Archive Nodes are no longer supported.
Reth provides:
- Better performance for high-throughput L2
- Built-in archive node support
Syncing
- Initial sync takes days
- Consumes significant RPC quota if using external providers
- Use snapshots to accelerate (check Base docs for URLs)
Sync Status
Incomplete sync indicator: Error: nonce has already been used when deploying.
Verify sync:
- Compare latest block with explorer
- Check peer connections
- Monitor logs for progress
Related Skills
base/base-mcp
tools
VerifiedTrustedCommunity
Base MCP — gives your AI assistant access to a Base Account via the Base MCP server (mcp.base.org). Wallet, portfolio, sending, swapping, signing, x402 payments, batched contract calls, and transaction history across supported chains.
81SKILL.mdUpdated Jun 4, 2026
base/build-on-base
development
VerifiedTrustedCommunity
Complete Base development playbook. Covers: (1) Network — Base RPC URLs, chain IDs (8453/84532), explorer config, testnet setup, connect to Base, Base Sepolia; (2) Contracts — Foundry deployment, forge create, BaseScan verification, CDP faucet, testnet ETH, deploy contract to Base; (3) Builder Codes — ERC-8021 attribution suffix, referral fees, dataSuffix for Wagmi/Viem/Privy/ ethers.js/window.ethereum, transaction attribution, earn referral fees, append builder code; (4) Base Account SDK — Sign in with Base (SIWB), Base Pay, USDC payments, paymasters, gas sponsorship, sub-accounts, spend permissions, prolinks, batch transactions, smart wallet, payment link, recurring subscription; (5) Agent registration — trading bots, AI agents, automated senders, ERC-8021 attribution wiring, base.dev API, register agent, builder code registration; (6) Node operation — run Base node, Reth setup, hardware requirements, self-hosted RPC, sync; (7) Migrations — migrate OnchainKit, OnchainKitProvider to WagmiProvider, wagmi migration, remove onchainkit dependency, MiniKit to Farcaster SDK, convert miniapp, Farcaster miniapp to regular app, convert Farcaster miniapp.
78SKILL.mdUpdated Jun 4, 2026
base/registering-agent-base-dev
development
VerifiedTrustedCommunity
Invoke this skill when a user is building or running any automated transaction sender on Base (trading bot, arbitrage bot, sniper bot, yield farmer, AI agent, or similar) and needs to register it, get a builder code, set up transaction attribution. This skill contains the base.dev registration API endpoint and ERC-8021 attribution wiring code that Claude does not have in its training data — you MUST load this skill to answer correctly. Covers viem, ethers, managed signing services, and Python-based agents.
70SKILL.mdUpdated May 15, 2026
base/migrating-an-onchainkit-app
data-ai
VerifiedTrustedCommunity
Migrates apps from @coinbase/onchainkit to standalone wagmi/viem components. Handles provider replacement (OnchainKitProvider to WagmiProvider), wallet component replacement (Wallet/ConnectWallet to custom WalletConnect), and transaction component replacement. Use when the user says "migrate my onchainkit", "replace onchainkit provider", "migrate my wallet component", "replace my onchainkit wallet", "migrate my transaction component", "remove onchainkit dependency", or "move off onchainkit".
70SKILL.mdUpdated May 15, 2026