KUB Developers

KUB Docs MCP is now available! Connect the KUB Docs directly to your AI coding assistant: Claude, Cursor, Gemini, Codex, whatever you build in. Ask about RPC configuration, KAP-20, deployment, and get answers grounded in the actual docs, no tab-switching.

Whitepaper V5.2 is out, and the direction is clear: Open Finance infrastructure, powered by AI tooling. Five years of KUB Mainnet, in numbers: - 5.11B+ transactions processed - $852M TVL - 2.43M+ wallets on-chain - 201,610+ KUB burned quarterly, tracked publicly at burn.kubchain.com The Open-Fi Roadmap: - Block time upgrading from 3s to sub-second - Native Real World Asset tokenization support - Zero-fee USDT bridging from Bitkub Exchange - THBK: a programmable Thai Baht, lives in a regulatory sandbox with merchant escrow For KUB Developers: KUB Docs MCP is live. It connects your AI assistant directly to KUB Docs, so the model already knows the network when you start building. How it works: Set up Claude, ChatGPT, Cursor, or Gemini on the KUB Docs MCP server. Describe what you want in natural language. The AI handles RPC configuration, token standards, contract deployment, and wallet connection. No more copy-pasting docs into your context window. What this unlocks: - EVM Developers: Skip the ecosystem ramp-up and build on the KUB network in your first session - Non-Developers: Go from idea to working smart contract and web interface without writing code - Everyone: Build utility apps with on-chain revenue streams Prompt in, app out. Now everyone can build on KUB, not just developers. Get started: docs.kubchain.com/build-with-ai/…

We are excited to announce that the KUB Whitepaper V5.2 is officially live! Dive into the latest technical updates, ecosystem advancements, and our roadmap for the future. Read the full whitepaper now to see what we're building next. 👇 kubchain.com/docs/EN_KUB_Ch… #KUB #KUBChain #Blockchain #Crypto #Whitepaper #Web3

Integrating a third-party token, oracle, or DEX into your protocol can accelerate development, but it also introduces your largest external attack surface. Even if a contract is deployed on KUB Mainnet and fully audited, assuming it is safe is a dangerous mistake. To protect your protocol and your users, every external component must be thoroughly vetted. Use this checklist before writing a single line of integration code. The Vetting Checklist 1. Analyze the Source Code - Never treat an external contract as a black box; you need to understand exactly what you are calling. Review the smart contracts specifically looking for admin overrides, pause mechanisms, and upgrade hooks—any of these can break your structural assumptions down the line. 2. Scrutinize the Governance Power - Identify who holds the keys to the contract. Is the admin a multi-sig, a decentralized DAO, or a single Externally Owned Account (EOA), which represents a massive security risk? Determine if the controllers can arbitrarily pause the contract, alter fee structures, or upgrade the core logic. 3. Review the Contract History - Past behavior is an excellent indicator of future risk. Look into whether the contract has ever been upgraded and under what circumstances. Search developer forums, GitHub issues, and social channels for past incidents, emergency pauses, or historical exploits. 4. Run Rigorous Testnet Simulations - Deploy and test your integration extensively on the KUB Testnet. Intentionally mock worst-case scenarios: - What happens to your protocol if the external contract suddenly pauses? - How does your code handle an unexpected revert? - What happens if it returns malformed or stale data? Build code fallbacks for each of these failure modes before moving to production. 5. Evaluate the Audit Validity - Not all audits carry the same weight. Verify the reputation of the security firm and check whether the engagement was a comprehensive, formal audit or just a cursory review. Most importantly, ensure the audit matches the exact commit hash of the code you are integrating, rather than an outdated version. 6. Architect a Clean Exit Strategy - You must design your off-boarding mechanism before something goes wrong, not after. Ensure your architecture is free of circular dependencies or locked liquidity that could trap user funds. Can you safely pause or decouple your integration without bricking your entire protocol? 7. Treat Integrations Like Team Members - Third-party smart contracts should be vetted with the same scrutiny you would apply to hiring a new core team member. By building defensively and planning for external failures, you ensure your app remains resilient. For more secure development standards on KUB, explore the developer resources at docs.kubchain.com

Bridge assets from various networks like Ethereum, BNB Smart Chain, and more to the KUB network using the KUB Bridge. Here's a quick guide to get you started. 👇 How it works: - Connect your wallet to the source network (e.g., Ethereum) at bridge.kubchain.com. - Select the token you want to bridge and the destination network. - Submit the transaction from your wallet. The funds will arrive on the destination chain within a few minutes. The assets that can be bridged depend on the token dropdown selector at bridge.kubchain.com. So, check there directly instead of assuming a fixed list. When building on bridged assets, consider the following: - The wrapped asset will have a different address on the KUB network compared to its origin chain. - Liquidity can vary; some bridged assets may trade thinly. - For payments, stablecoins are generally more predictable than volatile assets. However, verify that a specific stablecoin is actually supported before building around it. If you're building a DEX, payment processor, or lending protocol on the KUB network, familiarize yourself with the bridge mechanics. Your users will bridge assets into the network, and you'll be responsible for handling the bridged tokens. For more information, refer to the official documentation: docs.kubchain.com/tools/token-br….

Launch a KAP token on KUB in a few lines of Solidity. The npm package: kub-chain/contracts is live, built for KUB. For more information: @kub-chain/contracts" target="_blank" rel="nofollow noopener">npmjs.com/package/@kub-c…

Soon...

5/ Simple guidance: - Default to limited approval (amount-per-transaction) - Use permits if supported - Only ask for unlimited if the user explicitly opts in - Document why you need what you ask for Docs: docs.kubchain.com

4/ The better pattern: limited approval. Ask for the exact amount the user needs right now. token.approve(yourContract, amountForThisTransaction) User approves once per transaction (or once per session). Higher friction, but they know exactly what you can take.

1/ When a user interacts with your app, they approve your contract to spend their token. Most apps ask for unlimited approval (type(uint256).max). This is a security risk. Here's why and what to do instead 👇

7/ Once verified: source readable by anyone, functions callable straight from the explorer, and your users can check exactly what they're signing. Stuck on an error? Reply here; we're around. Docs: docs.kubchain.com

6/ Where to get the Standard JSON input? After npx hardhat compile, it's the input field inside artifacts/build-info/*.json. Upload, add constructor args if your contract has them, Verify & Publish.

1/ Verifying your smart contract on KUB Scan takes five minutes and is the cheapest trust signal you can ship: your source code becomes public, readable, and directly interactable on the explorer. Two ways to do it: straight from your CLI, or through the UI 👇

KUB Burn is live. Each quarter's burned KUB, permanently removed from the circulating supply, is now visible and auditable in one place. For more information, visit: burn.kubchain.com

3/ After that, you'll receive 5 tKUB in just a few seconds. If you want to check your balance instantly, paste your wallet address on testnet.kubscan.com to view your current tKUB balance. Keep building!

2/ To get started, head over to faucet.kubchain.com and paste your wallet address. Then, click Receive Tokens.

1/ Wondering how to get started on app development or need tKUB to deploy a contract on the KUB Testnet? We've got you covered right here! No signup, no waiting. Check it out! 👇