Anyone can launch a token on KForge. There is no approval process, no whitelist, no form to fill in. You call the contract and the token exists. But permissionless doesn't mean unprotected. Every rule that matters: the price, the fee, the supply cap is written into the covenant script that holds the funds. The script runs on every node in the Kaspa network. No single server decides whether your transaction is valid. Most launchpads have a sequencer: a server that sees transactions before they land on chain and can reorder, delay, or front-run them. KForge has no sequencer. When you buy or sell, your transaction goes straight to the network. The covenant checks it. There is no intermediary that can see it first. The backend we run assembles transactions and pays the network fee on your behalf, that's a convenience. It cannot change the price you were quoted, take your tokens, or block you from trading. The covenant wouldn't let it through if it tried.

$KFORGE fair launch - date and time coming soon. 1 billion fixed supply. No presale. The bonding curve is the only way in. Each transaction on the bonding curve is capped at 50M tokens (5% of supply). We want the launch to be as open and permissionless as possible, the cap means no single buyer can take a large slice before everyone else gets a chance. Once $KFORGE graduates into the open market pool, the cap is gone and trading is unrestricted. Next up for $KFORGE: stake to earn a share of protocol revenue from every trade on the platform, ongoing buybacks, and access to the KForge trading agent we're building. More details → kforge.xyz/token.html

How a KForge token graduates, and why it matters Most launchpads end at a bonding curve. The team takes the raised funds, adds liquidity somewhere, and you trust them to do it honestly. KForge doesn't have that step. When the last of 800 million tokens sells on the curve, graduation happens automatically. Here's what the covenant actually enforces. The curve's final transaction must create a pool with exactly the right outputs. The script checks: The new pool receives the exact KAS the curve raised, to the sompi The pool's token reserve receives exactly 200 million tokens, the amount held back at launch The pool token is owned by the pool covenant ID, not by any wallet The pool contract bakes in the creator's fee address, the protocol fee address, and the 1% fee, all fixed at forge time If any of these checks fail, the transaction is invalid. The node rejects it. There is no "close enough." This is what a Kaspa covenant actually does: it constrains what outputs a spending transaction is allowed to create. The script running inside the UTXO says "I will only allow myself to be spent if the transaction that spends me creates these specific outputs at these specific amounts going to these specific addresses." Violating any condition means the transaction never confirms, no matter who signs it. The result: graduation cannot be short-changed. The liquidity cannot be redirected. The creator cannot take the raised KAS and run. Nobody can. It is enforced by the chain, not by a multisig, not by a timelock, not by a promise. After graduation the pool has no owner. There is no address that can drain it, no function that can change its fee, no upgrade path. It runs on Kaspa and will keep running for as long as Kaspa does. This is only possible on L1. A smart contract platform can simulate some of this, but the execution environment itself can be paused, upgraded or exploited. Kaspa covenants are consensus rules. The only way to change them is a network-wide hard fork. testnet.kforge.xyz kforge.xyz/how.html

KForge is built on Kaspa L1 covenants. Here is what that means in practice. No custody You never send funds to us. Every trade starts with a plain KAS transfer from your own wallet to a one-time script address. That script can do exactly two things: complete your trade at the price you were quoted, or return the deposit to you. It cannot send your funds anywhere else. We cannot touch them. No admin key Every token's price, fee and supply is written into its covenant at launch and cannot be changed. There is no upgrade function, no pause button, and no owner who can drain the pool. When a token graduates into an AMM pool, that pool has no owner field. It exists on Kaspa and runs by its own rules. No sequencer We do not decide the order your transaction is processed in. You send directly to the chain. We cannot front-run your trade, censor your wallet, or delay your transaction. If our servers go offline the contracts keep working. No discretion over fees Creator rewards are set at forge time and paid directly by the pool on every swap. We cannot change the destination, reduce the amount, or hold it back. The covenant enforces it. Verifiable on chain Every token, every trade, every pool reserve is public on Kaspa. Anyone can verify the state of any contract without asking us. The interface is ours. The protocol is the chain's. testnet.kforge.xyz

We heard the community loud and clear. The presale idea is being scrapped. $KFORGE will fair launch on KForge itself. No presale. No early-buyer discount. Everyone enters through the same curve. It’s the approach that best reflects what KForge is being built to be: a truly permissionless launchpad built directly on Kaspa L1 where decentralization is a guarantee and not just a promise. Full launch details will be announced soon. For now, we’re continuing to polish the protocol and waiting for the final KCC-20 standard so we can make the necessary adjustments.

Getting mixed feedback on how $KFORGE should launch. Want your input. 🔵 Presale + public sale: upfront funding, early-buyer discount, but allocations from day one. 🟢 Fair launch on KForge: same curve for everyone, funded by fees, but no funding Which approach you prefer?