Your contract is on the KUB Testnet. Now your users need a frontend to interact with it. The KUB Docs "Build an App on KUB" guide walks through a small Next.js app using wagmi and viem that connects a wallet, reads from a contract, and writes to it. Setup uses tools you likely already know: create-next-app, then wagmi, viem, and TanStack Query. Recent viem versions include KUB definitions (bitkub and bitkubTestnet in viem/chains). You can also define KUB Testnet (Chain ID 25925) and KUB Mainnet (Chain ID 96) yourself with defineChain, which works on any version. The guide also covers three details that cause real bugs. First, handle the wrong-network case. KUB is a custom network in MetaMask, so first-time users are often on another chain. Without useSwitchChain, the write button can stay on "Confirm in Wallet" forever if the user misses the popup. Second, declare your ABI with "as const", or wagmi cannot infer function names and types. Third, use ssr: true with cookieStorage and cookieToInitialState so the connection state doesn't flash on page load. Also remember to fund the browser wallet from the KUB Faucet, not just your deployer key. When your app is ready, submit it to the KUB Developer Center to be listed in the KUB Ecosystem directory. Build it step by step: docs.kubchain.com/quickstart…