Built an app on KUB and want it on the KUB Wallet app page? There's no form to fill in and no inbox to chase. Listings live in a public GitHub registry, and you add your app by opening a pull request. Check the requirements before you start. Your app must be live on KUB Mainnet, its contract source must be verified on KUB Scan, and it must be served over HTTPS with a valid certificate. The domain has to be one your team controls and has been registered for at least 90 days. Submitting takes three steps: fork github.com/kub-wallet/apps, add one directory containing your app.json, icon, and screenshots, and open a PR. Automated checks run within minutes. They confirm that the domain resolves, the certificate isn't close to expiry, the URL doesn't redirect to a different domain, your contracts exist and are verified on mainnet, and the domain isn't on a phishing blocklist. If a check fails, push fixes to the same branch rather than opening a new PR. Passing the checks makes your submission ready for review; it doesn't add the app yet. A reviewer then uses your app and reads what it asks users to sign, so plan for 7 to 14 business days and expect questions. Every addition needs two approvals, one of them from security, and approved apps ship in a weekly release. After you're listed, apps are re-verified every 90 to 180 days. Treat a domain change as a new submission and tell the team before you migrate. If your app has its own token, submit that separately through the Add New Tokens guide. The full guide is here: bitkub-blockchain.gitbook.io…. A listing is not a partnership, audit, or endorsement. It does give KUB Wallet users a reviewed path to your app.

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…