Most token launchpads are built on top of a chain. KForge is built into one. Every KForge trade is enforced directly by covenants on Kaspa L1 no sequencer, no admin key, no contract owner who can change the rules. The covenant holds the funds and enforces the price, fees and supply. If the rules allow it, it happens. If they don’t, it can’t. The contracts aren’t infrastructure behind KForge. They are the product. Live on testnet: testnet.kforge.xyz How it works: kforge.xyz/how.html

Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday. You can play it here: vprogs-tt.izio.fr/ (Requires private key and some testnet funds) We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top For Devs: this is the invitation. Play the game, read the code, build your own vprog. Game code: github.com/biryukovmaxim/vpr… vprogs framework: github.com/kaspanet/vprogs/t…

Why build launchpad directly on Kaspa L1? Because Kaspa’s emerging covenant capabilities make it possible to build far more expressive systems directly around its UTXO model. For KForge, covenants can define and enforce the rules governing token launches, bonding curves and liquidity at the L1 level. The rules live in the transaction logic rather than depending on KForge running a centralized backend to decide what is allowed. Combined with Kaspa high-throughput BlockDAG architecture, this gives us a path toward a launchpad that stays close to the properties of the underlying network: • L1 execution and settlement • Covenant-enforced rules • UTXO-based state • No separate sequencer • Permissionless participation • No centralized party approving launches And there is no requirement to own $KFORGE to launch a token. $KFORGE is optional, for those who want to participate in the Kforge ecosystem. It is not intended to become a toll gate standing between users and Kaspa. The goal is simple: use what Kaspa makes possible at L1 instead of rebuilding unnecessary centralized infrastructure on top of it.

KForge is live on Kaspa testnet, and you can try all of this today. Launch a token and you get paid for as long as it trades. Half of every pool swap fee goes straight to your wallet, paid by the pool itself. No claiming, no team handing it over, and the destination is fixed when you forge so nobody can change it. Built in, to help your token go somewhere: Competitions with prizes you set, over any window you choose, standings tracked live Referral links that attribute trades to whoever brought them A creator page showing your tokens and earnings, ready to share A leaderboard ranking tokens by volume and creators by fees earned Forging is free, and there's no pre-mine: if you want your own token, you buy it on the curve at the same price as everyone else. Try it: testnet.kforge.xyz How it works: kforge.xyz/how.html

Mark your calendar: the $KFORGE presale opens 1 October, 16:00 UTC. KForge goes live on Kaspa mainnet once KCC20 is finalised. The protocol is built and running on testnet, with forge, curve, graduation and pool all working, and the remaining work down to polish. $KFORGE is the token behind it. Presale price 0.15 KAS, which is 33% below the public sale at 0.225 KAS $50 minimum, $5,000 maximum per wallet KAS only, first come first served, every allocation on a public ledger 100,000,000 fixed supply, no minting ever Revenue share paid in KAS, buybacks, and deeper pools for new launches Pay from your own Kasware wallet, never from an exchange $KFORGE is issued at the mainnet launch, presale allocations are delivered then, and the public sale follows. Try it on testnet: testnet.kforge.xyz Presale and countdown: kforge.xyz/sale.html

Full walktrhough how KForge works, in one page: Forge a token for free, 1B fixed supply 800M sold on a bonding curve, price rising every step At 800M sold, it graduates into a pool nobody owns 1% pool fee, half paid straight to the creator on every trade No custody: you sign one transfer, the script does the rest Competitions, referral links and creator pages built in Live on testnet: testnet.kforge.xyz Full walkthrough: kforge.xyz/how.html

This onchain message below is an official communication from Igra Labs regarding the KRC-20 incident on 20 September. Read and verify the message: explorer.igralabs.com/tx/0x6… Full text: "To the controller of 0x1B4B7108a49F028598c5ED49B7951c80d44e7FD2 and kaspa:qzfkfuhlswdpemz6qe82squt973kjawx9jax5rn6zrln2533trp0j44cuf43u. We are contacting you regarding the KRC-20 incident of 20 September 2026. We are seeking the full return of the assets obtained through it, including the iKAS now held at 0x9cc770e5b30f8179ddca2d8dd3d73548829af546 and 0x17030b7ea819a8742f6cec5114733267f14140ab. Exchange-linked funding of this operation has been identified. Return the funds to 0xB3300fcC2F3EF3DeCdF8B1f710c21666f33Cbf18 on Igra (chain ID 38833), or contact team@igralabs.com within 72 hours of this transaction's block timestamp to coordinate the return."

$KFORGE the token behind Kforge launchpad directly on Kaspa L1 100,000,000 fixed supply, no minting ever 20% public sale, liquid at launch 10% presale, 10% at launch, rest vested over 12 months 15% graduation liquidity for new token pools 13% ecosystem and partnerships 13% reserve, published unlock schedule 10% team, vested over 2 years 9% exchange listings, 8% protocol liquidity, 2% marketing Utility: Revenue share from launchpad fees, paid in KAS Buybacks and burns Deeper pools for graduating tokens, future Kforge ecosystem project and expansion Launches on KCC20 once the standard is final. Prices and dates to follow. Full details here: kforge.xyz/token.html

Kforge Testnet has been reset. An audit turned up issues in the covenants. Several were exploitable: value a contract calculated but never bound to an actual output, a pool that could declare reserves it didn't hold, a way to move another holder's tokens during a consolidation. Fixing them meant changing the contracts. A Kaspa address is the hash of its script, so new scripts mean new addresses — every token launched before today is untradeable and has been hidden. There was no migration that preserved positions. That's the cost of finding things before mainnet rather than after. One finding is worth mentioning because it wasn't a vulnerability at all. The AMM's constant-product check was approximate, and while chasing a rounding bound we found it was also rejecting valid trades, ordinary sells at any pool size, failing on arithmetic rather than economics. It's now exact. That surfaced only because the review refused to accept tests that proved less than they claimed. Everything is relaunched and working: forge, buy, sell, graduate, swap both directions. Testnet nodes are being flaky today, so prices and balances may lag a minute behind the chain. The trades themselves settle in seconds. If you had a deposit funded but not settled, it's no longer reachable through the new contracts. Get in touch and we'll sort it. More resets are possible. That's what testnet is for.