Kaspero Labs said on Monday that its Kozmic Bridge, which moves USDC between Ethereum and Kaspa’s base layer, is close to opening. The announcement, posted at 2:08 p.m. ET on Nov. 16, describes a bridge where each chain checks a zero-knowledge proof of what happened on the other, with no signers holding keys in the middle.
The project’s public GitHub repository says the contracts are already deployed on mainnet with real USDC. As of about 8 a.m. ET on Tuesday, the Ethereum vault held 200.10 USDC, according to a KaspaNews query of the USDC contract. The team says it wants “a few more rounds of testing before the door opens.”
How Kozmic differs from kUSDT
The announcement came a day after Trestly launched kUSDT, a bridged USDT token on Kaspa. Both tokens use KCC-20, a token format that became possible with the Toccata hard fork in June. A KCC-20 token lives in covenant outputs, coins whose spending rules every Kaspa node checks. Older KRC-20 tokens, by contrast, rely on off-chain indexers to track balances.
The difference is in who you trust. kUSDT is minted and released by a 3-of-5 signer group.
Kaspa developer saefstroem (@asaefstroem), who is involved in the separate KaspaDollar stablecoin project, summed it up early Tuesday: “the security of kUSDT is the security of: 1. Trusting the signers 2. Inherits the security of PoS/PoA properties of $BNB and $ETH.” Trestly developer kaspador (@kaspador_) replied: “Correct, as almost every bridge out there is doing.”
Kozmic tries to remove the signers. According to its README, a deposit into an Ethereum vault is proven to Kaspa with a proof of Ethereum’s finality, built on RISC Zero and a16z’s Helios light client. A Kaspa covenant checks that proof using the zero-knowledge verification opcode added in Toccata (KIP-16), then mints the same amount of a KCC-20 token called kzUSDC. In the other direction, a user burns kzUSDC and a prover shows Ethereum enough Kaspa proof-of-work mined after the burn to release USDC from the vault.
Kaspero says deposits take about 25 minutes and exits about 90 minutes. The README says exits of up to about $1,200 take roughly 90 minutes, and larger ones wait longer because the proof must carry more Kaspa work.
Proofs are heavy. Kaspero Labs said one takes “about 70 seconds” on an RTX 4090 GPU and “almost 2 hours” on a 12-core CPU. Anyone can run a prover; Kaspero runs one today.
Caps, risks and what is not checked
The limits are deliberately small. In a reply on X, Kaspero Labs said: “Total bridged: $5,000 this week, doubling every week up to $1M. Up to $10,000 per transfer. Exits pay out at most $25,000 a day.” It said the caps are written into the vault contract and cannot be changed, adding: “Small on purpose while it proves itself.”
The project’s own RISKS.md is blunt. “No paid audit has been done,” it says.
The vault, relay and covenant cannot be upgraded, so a bug means closing the instance and deploying a new one. Circle can blacklist the vault, which the document says would be “a total loss for holders who have not exited.” The README also notes that the exit proof does not verify GHOSTDAG ordering, the rule Kaspa’s BlockDAG uses to order parallel blocks; security rests on counting high-difficulty Kaspa blocks mined after the burn.
The record so far is short. The README says a first instance ran with real USDC from Nov. 15, with one deposit in 24.5 minutes and a first exit in 71.6 minutes. Another exit took 3 hours 38 minutes when a GPU provider’s API quota ran out. A second instance was deployed on Nov. 16 after an external review, and the first was closed to deposits.
Community analyst Mirek (@BaierMiroslav) wrote that “the risk doesn’t vanish, it moves into the circuits and contracts. So it needs a serious audit before it gets serious money.”
Why it matters
For holders, Kozmic would be the first bridged dollar on Kaspa that does not rely on a signer committee, if it opens as described. Even so, the trust moves rather than disappears. Users still rely on Ethereum’s validators, Kaspa’s hashrate, RISC Zero’s proof system and Kaspero’s code. Kaspa’s hashrate stood at about 323 PH/s on Tuesday’s daily reading from api.kaspa.org, about half the 629 PH/s reading of a year earlier, and that figure matters directly for a bridge whose exits lean on proof-of-work.
For builders, the code is readable but not freely reusable. Most of the repository uses the Business Source License 1.1, so running a copy as a mainnet bridge requires a commercial license from Kaspero Labs until Nov. 16, 2030, when it converts to MIT.
Trestly is moving too. It said on Nov. 16 that its bridge works with KasWare, Kastle and Kaspire wallets, and on Tuesday that a kUSDT Wallet extension is live on the Chrome Web Store. Kaspador said on X that kUSDT’s code is still not audited.
What to watch
A public opening date for Kozmic and the live cap figures on its page.
Whether either bridge commissions a paid audit.
kzUSDC and kUSDT supply, and which wallets and pools list kzUSDC.
KForge, a token launchpad built on Kaspa, opened version 2.0 on the network’s public testnet on Monday, adding AI agents that can launch and trade tokens on their own. The team announced the release at 4:21 a.m. ET on Nov. 16 and published its agent software as an open-source package on GitHub the same morning.
A day later, KForge reported that nine agents had made 499 trades in the first 24 hours. “They’ve launched 15 tokens, traded about 3,500 testnet KAS between them, and they’re up 3.8% combined,” the team wrote. Those figures come from KForge itself and have not been independently checked. Everything runs on testnet coins, which have no market value.
What KForge 2.0 does
KForge describes itself as a fair launchpad. On its mainnet site, every token starts on a bonding curve, a pricing formula where the price rises as more is bought, and then moves to a liquidity pool “nobody owns.” Version 2.0 adds a second section where the creators and traders are AI agents rather than people.
There are two ways to run one, according to the project’s README. Users can install a KForge extension in Claude Desktop and give instructions in chat, such as asking what is trending or telling it to buy a token. Or they can run a command-line tool, npx kforge setup, give the agent a plain-language strategy and let it trade on a loop. KForge says every agent starts in paper mode, which simulates trades at real prices, and needs a typed “go live” confirmation before it trades for real.
The team stresses key handling. “Keys never leave your machine,” the launch post said.
The README adds that each transaction is checked locally before signing, that spending and launch limits are enforced in code, and that KAS can only be withdrawn to an address the user sets. It also says text written by token creators or other agents is passed to the AI “as untrusted data, never as instructions,” a defense against prompt injection, where a malicious message tries to hijack an AI agent.
Agents can only trade tokens launched by other agents, though people can trade those tokens too. A public leaderboard ranks agent performance. KForge said six agents were already trading when it launched.
The GitHub repository was created at 3:55 a.m. ET on Nov. 16 under an MIT license. Its first commit is labeled “kforge 0.1.0,” and four more had followed by Tuesday morning.
Background: why this can run on Kaspa’s base layer
Kaspa is a proof-of-work network built as a BlockDAG. Instead of a single chain where competing blocks are thrown away, it keeps parallel blocks and orders them with a rule called GHOSTDAG, producing about 10 blocks per second. Since the Toccata hard fork on June 30, 2026, Kaspa supports covenants, coins whose spending rules every node enforces, which lets apps such as launchpads and pools run on layer 1 rather than on a separate chain. KForge’s announcements did not say which token standard its launches use, and KaspaNews could not confirm it.
KForge is one of several projects testing apps on the base layer this month. A testnet order book called KOB opened Nov. 12, and Trestly’s bridged kUSDT went live on mainnet on Nov. 15.
Why it matters, and the caveats
For builders, the open-source agent code is a working example of how to let software hold keys and transact on Kaspa with hard limits. For holders, it is an early test of whether automated trading will bring activity to Kaspa-native tokens. Demand so far is thin. When KaspaNews retrieved the KForge mainnet site on Tuesday, the top tokens on its front page showed no 24-hour trading volume, and the largest pool held about 40,000 KAS of liquidity, roughly $1,100 at Tuesday’s price.
There are reasons for caution. Agents launching tokens for other agents to trade is a fast way to create many low-liquidity assets.
A 3.8% combined gain on testnet says little about how the same strategies would perform with real money, and AI models can make mistakes, and real-money agents could lose funds. Community account @KasCryptoKing reminded readers on Monday that not every launch involves real coins: “Testnet: a practice network. Addresses start with ‘kaspatest:’ and its coins aren’t real KAS.”
Not everyone was dismissive. Commentator @Ashishrathodind called it “Impressive technical progress,” then asked whether it “Can this evolve into real utility?” He pointed to payments and machine-to-machine commerce as the bigger opportunity.
KAS traded at about $0.0273 on Tuesday morning, down about 9% over seven days, according to CoinGecko, with roughly $8.4 million in 24-hour volume. Its market value was about $759 million.
What to watch
A date for the mainnet release, which KForge said will be shaped by testnet feedback.
Whether an outside security review of the agent tool is published.
Agent leaderboard results over a longer period and with more agents.
Kaspa’s network hashrate stood at about 328 petahashes per second (PH/s) on Monday, Nov. 16, according to daily data from api.kaspa.org. That is down about 13% from 379 PH/s a month earlier and roughly 48% below the 631 PH/s recorded on the same date in 2025.
The next scheduled cut to Kaspa’s block reward lands on Dec. 5 at 00:28 UTC (7:28 p.m. ET on Dec. 4). The reward will fall from 1.9445 KAS to 1.8354 KAS per block, a reduction of about 5.6%.
The figures matter for miners because the KAS price has also fallen. CoinGecko listed KAS at $0.0266 on Monday afternoon, down 11.4% over seven days and 24.3% over 30 days.
How Kaspa mining works, and the long slide
Kaspa is a proof-of-work cryptocurrency that launched in November 2021 without a premine. Its ledger is a BlockDAG, a structure that keeps blocks mined at the same moment instead of discarding them, and orders them with a protocol called GHOSTDAG. Miners use the kHeavyHash algorithm, mostly on dedicated ASIC machines.
Kaspa does not halve rewards every four years like Bitcoin. Its emission falls a little every month, on a curve that halves the reward once a year. The Dec. 5 step fits that pattern. The ratio of the new reward to the current one is 0.9439.
Network data shows the chain producing about 10 blocks per second, or 864,505 blocks in the 24 hours to Monday afternoon. At the current reward, that works out to roughly 1.68 million KAS a day in new coins, or about $44,700 at Monday’s price. That is a KaspaNews calculation from public API data and excludes transaction fees. Circulating supply is 27.81 billion KAS out of a 28.70 billion maximum, about 96.9%.
Hashrate has been falling for most of the past two years. Daily data from api.kaspa.org shows a peak of about 1,481 PH/s on Feb. 1, 2025. Monday’s level is about 78% below that.
The decline was steady through 2026. Hashrate sat near 441 PH/s in early February, around 410 PH/s in early June, and about 357 PH/s on June 30, the day the Toccata hard fork went live. Over the past 30 days it has ranged between about 316 and 382 PH/s.
Lower hashrate means less computing power securing the chain. Kaspa’s difficulty adjusts continuously, though, and the block rate has held at its target.
What miners and analysts are saying
The weekend brought renewed attention to large miners.
Crypto Matt (@cryptomatt1983) wrote on Nov. 15 that “the MARA wallet has started to receive KASPA deposits from F2Pool,” adding that it “could indicate them turning mining machines on again or simply receiving final payouts from the pool.” KaspaNews could not confirm the wallet’s ownership or what the transfers mean, and MARA has not commented. Treat this as unconfirmed.
Some holders worry about the long-term security budget as rewards shrink. “Now is the time to drive network activity bc mining emissions are getting so low,” wrote FinanceFreeman (@FinanceFreeman). “Need to keep network secure.”
Merge mining is part of that debate. Checker.Crypto (@Checker1crypto) claimed that ZKAS, a project built from Kaspa’s code that uses the same proof-of-work, “already runs on 22.8% of $kas hashrate” because it is merge-mined alongside Kaspa. KaspaNews has not independently verified that figure.
Others are skeptical that side tokens can fill the gap. “Merge mining is not some secret magic pill that just solves miner revenue for good,” wrote KaspaSilver (@KaspaSilver).
Why it matters
For miners, revenue per machine depends on three things: the block reward, the KAS price, and total network hashrate. The first two are falling. Some of that is offset as less efficient machines switch off, which raises each remaining miner’s share of the reward.
For holders, the security budget question is long-term rather than immediate. Transaction fees and new on-chain activity, including covenant applications launched since Toccata, are the main ways the network could pay miners as emission falls.
What to watch next
Hashrate around the Dec. 5 reward step, and whether it holds above the 30-day low of about 316 PH/s.
Any public statement from MARA on its Kaspa operations.
Fee activity from new applications such as the kUSDT bridge and KasPool, which went live on Nov. 15.
Announcements from ASIC makers and mining pools on new hardware or Kaspa-related merge-mining support.
Kaspa’s core developers pushed new work on DAGKnight, the consensus protocol planned to replace GHOSTDAG, over the weekend. Pull request #1168 was merged into the dagknight branch of the rusty-kaspa repository at 11:17 p.m. ET on Sunday, Nov. 15. A second pull request, #1172, which implements the protocol’s “applied” tiebreaking rule, was opened Sunday morning and remains under review.
GitHub records show #1168 is the first pull request merged into that branch since Sept. 8. The same weekend, the main branch gained a formal security policy that describes how to report vulnerabilities and how community-funded bug rewards are paid. No activation date for DAGKnight has been announced.
What DAGKnight is, and what changed this weekend
Kaspa is a proof-of-work network that uses a BlockDAG. Blocks created at the same time are not discarded as orphans, as on Bitcoin. They are kept and ordered. Today that ordering is done by GHOSTDAG, which relies on a fixed parameter, k, chosen to fit an assumed worst-case network delay.
DAGKnight is designed to remove that fixed assumption. Instead of hard-coding a delay bound, it is meant to adjust to how the network is actually performing. Developers and supporters have linked it to plans for higher block rates. Kaspa currently runs at about 10 blocks per second; api.kaspa.org data showed 864,505 blocks in the 24 hours to Monday afternoon.
PR #1168, titled “[DK] DK store rename and BFS coloring semantics,” was written and merged by the GitHub user coderofstuff. It changes 16 files, with 805 lines added and 724 removed. It renames the DagknightStore to ConflictZoneColoringStore and returns the code to coloring “the full zone bottom-up to prepare for follow-up related to shortcuts and coloring changes,” according to the PR description.
PR #1172, “Tiebreaking applied,” was opened by the GitHub user biryukovmaxim at 8:31 a.m. ET on Nov. 15. It touches 3 files, adding 627 lines and removing 324.
The description says it “replaces the Algorithm 4 witness tiebreak with the applied rule,” and changes which competing sides of the DAG reach the tiebreaking step. Tiebreaking decides the outcome when two competing groups of blocks are closely matched. The dagknight branch is now 130 commits ahead of master and 21 behind it, according to GitHub’s compare view.
Community accounts tracked the changes within hours. “DAGKnight just moved again,” wrote Kaspius Maximus (@KaspiusMaximus).
The post continued: “Overnight, PR #1168 was merged into rusty-kaspa’s dagknight branch: the first DK merge since September. Next up: #1172 ‘Tiebreaking applied’.” It added: “The goal: consensus that adapts to real network latency. No activation date yet.”
Daniel_Kaspa (@Daniel_Kaspa_KR) summarized #1172 as “OPEN | CI PASSED | NOT MERGED,” and wrote that “when competing block groups are closely matched, DAGKnight needs a deterministic way to choose.”
The pace is worth stating plainly. Before this weekend the branch had gone more than two months without a merged pull request, and two other DAGKnight test PRs (#1131 and #1132) were closed without being merged. Research-heavy consensus work tends to move in bursts. Holders waiting on a launch date have none to point to.
A security policy for the node software
On the main branch, PR #1171 added a SECURITY.md file. It was authored by GitHub user someone235 and merged by michaelsutton at 9:58 a.m. ET on Nov. 15.
The policy asks researchers to report vulnerabilities privately through GitHub’s security advisory tool and not to discuss them on GitHub issues, X, or Discord before a fix is coordinated. It also writes down a community-funded reward process. Maintainers classify confirmed bugs as Critical, High, Medium, or Low, with Critical “intended for consensus-critical vulnerabilities.” After a fixed release and a waiting period for node operators to upgrade, they open a 14-day community fundraiser and split the proceeds among researchers.
That model has a clear limit. Payouts depend on what the community donates, so researchers are not promised a fixed bounty.
Why it matters
For node operators and exchanges, DAGKnight is a future consensus change. When it ships it will need a hard fork and a coordinated upgrade, as Crescendo and Toccata did. Nothing in this weekend’s changes requires action from node operators.
For builders, DAGKnight is relevant because many plans for faster block rates depend on it. Applications that rely on quick confirmations, such as the covenant-based apps that appeared after the June 30 Toccata hard fork, would be affected by any change in block timing.
For security researchers, the new policy gives a documented route for reporting bugs in the node software and a defined, if donation-based, reward path. It also sets an expectation that bugs will not be aired publicly before a fix is out.
What to watch next
Review and merge of PR #1172, and any further “[DK]” pull requests on the shortcut and coloring changes that #1168 prepares for.
Michael Sutton (@michaelsuttonil), a Kaspa core researcher, is due to appear on Vlad Costea’s livestream on Tuesday, Nov. 17, at 2 p.m. ET. “He will talk about his research work at Kaspa, covenants, ZK stuff & more!” Costea (@Vladcostea) wrote. Any timeline comments on DAGKnight would be news.
A testnet deployment of DAGKnight, which would come before any mainnet activation.
Trestly, a bridge project building on Kaspa, launched kUSDT on Kaspa mainnet on Sunday, Nov. 15. The token is USDT locked on Ethereum or BNB Chain and issued 1:1 on Kaspa’s base layer, alongside a KAS/kUSDT liquidity pool called KasPool. Trestly announced the launch on X at 3:09 p.m. ET.
“Trestly is live on mainnet. The first native USDT on Kaspa L1,” the project wrote from @trestly_io. “Not an indexer token. Not an L2. kUSDT is enforced by Kaspa’s own consensus through covenants (KCC-20), bridged 1:1 from Ethereum and BNB Chain.”
The token is not issued by Tether. The launch also comes with caveats that Trestly states openly: the system has had no independent audit, and its bridge depends on a group of off-chain signers.
What launched, and how it works
Kaspa is a proof-of-work network built as a BlockDAG. Instead of a single chain where competing blocks get thrown away, it keeps parallel blocks and orders them with a consensus rule called GHOSTDAG. Since the Crescendo upgrade it produces about 10 blocks per second. On-chain data from api.kaspa.org showed 864,505 blocks over the 24 hours to Monday afternoon, or 10.01 per second.
Kaspa’s first token standard, KRC-20, works through indexers. The network records the data, but token balances are computed by outside software such as Kasplex.
KCC-20 is newer. It uses covenants, which went live with the Toccata hard fork on June 30, 2026, so that token rules are checked by every Kaspa node. A covenant is a coin whose spending conditions require the transaction to create a valid next state.
According to Trestly’s open-source repository, published on GitHub under the account kaspador, kUSDT is minted only by a BridgeMint covenant. Minting needs signatures from 3 of 5 independent signers confirming a deposit into Trestly’s vault contract on Ethereum or BNB Chain. Withdrawals also need 3 of 5 signers and then wait 10 minutes in the vault, during which a pause can stop them. Trestly says the vault contracts cannot be upgraded and are owned through a 2-of-3 Safe multisig with 48-hour delays on changes.
The kUSDT and KasPool genesis transactions were both accepted on Kaspa mainnet at about 6:05 a.m. ET on Nov. 15, according to the Kaspa block explorer API.
Criticism and open questions
Kaspa explainer account vertex (@KaspaScopio) pushed back on the “native USDT” framing within hours. “USDT on Kaspa? Not exactly. Trestly has deployed kUSDT and a KAS/kUSDT pool on Kaspa mainnet. But kUSDT isn’t issued by Tether,” the account wrote.
In the same thread it flagged the trust model. “The security trade-off matters: minting and payouts require 3 of 5 bridge signers,” it wrote, adding that Trestly “has published the contracts and deployment records, but not all off-chain services.” It later said it had verified the genesis transactions on-chain but had not “independently tested deposits, withdrawals or swaps.”
Trestly’s own documentation is blunt. Its README says “No independent audit and no legal review have been done” and tells users to bridge “only what you can afford to lose.”
The project’s known-limits page says three stolen signer keys could mint at most 100,000 kUSDT at once and 200,000 in any 24 hours. Trestly says it cut that ceiling from 500,000 on Nov. 14 after reviewer advice.
Its status page, dated Nov. 15, said the launch was “in progress” and that the web app would open after final checks. Early users raised practical points too. Kaspian Nomad (@KaspianNomad) said the pool “needs more polish, specifically for pool contributors,” noting “there is no way to know how much you’ve made or how much volume is clearing the pool.”
Why it matters
Stablecoins are the main trading unit on most smart-contract networks, and Kaspa’s covenant apps have had little dollar liquidity to work with. A KCC-20 stablecoin gives builders of the newer covenant apps, such as the Kaspa Order Book (KOB) that opened on testnet last week, a dollar unit to trade against KAS.
Mighty, who runs the Kaspa Live block visualizer (@MightyPetrCoin), reported that “KasPool’s first liquidity deposit brought in 99,990 KAS and 2,700 kUSDT.” That is a small pool: the KAS side was worth about $2,660 at Monday’s price of $0.0266 (CoinGecko).
For holders, the trade-off is trust. Mirek (@BaierMiroslav) compared kUSDT with KaspaDollar (KSD), a separate KAS-backed stablecoin project that is still raising funds: “kUSDT = the dollar everyone knows, but you trust Tether plus the bridge. KSD = no admin key, but the peg lives or dies on KAS.” KaspaDollar reported on Nov. 14 that 628,030 of its 5,000,000 KAS target had been raised.
Wallet support is starting. The developer account nodor (@kaspador_) said on Monday it had added support for the KasWare wallet and Kaspire (@kaspirewallet) to work alongside the kUSDT wallet.
What to watch next
Whether Trestly’s web app and Reserves page open publicly on mainnet, and whether on-chain reserves match kUSDT supply.
Any independent audit, and publication of the off-chain signer and monitor code.
Trestly says a future version could mint against zero-knowledge proofs of deposits using Toccata’s KIP-16 opcode, replacing signer attestations for that direction. It gives no date.
Liquidity depth in KasPool, and whether exchanges or other wallets support kUSDT.
Kaspa’s fungible-token convention, KCC-20, is in last call. That’s the last public review before the spec can be marked final.
The header in the kaspanet/kccs repository says Status: Last Call. Michael Sutton merged the pull request that put it there on October 7. The official Kaspa account followed on October 11, saying the reference implementation is merged and open for developers to test. On October 14 the status line still says last call. It does not say final.
What last call actually means
A Kaspa Call for a Convention moves from idea to draft, then review, then last call, then final. Last call is the stretch where people are supposed to find the mistakes before wallets and apps start building on the text. KCC-0, the process document, is already final. It says an editor sets an end date for that stretch, usually about 14 days out, and that the date belongs in the header.
The KCC-20 file doesn’t have one.
So the review is open, and there isn’t a published end date on the spec. If the comments force a real change to the rules, the process sends the document back to review instead of waving it through.
The authors on the file are Sivan Helfer, Michael Sutton, Ori Newman and Romain Billot. It was created August 21. Helfer, who posts as Manyfest, wrote on October 7 that KCC-20 had moved to last call, and that writing a standard is a different job from writing a piece of software. A standard is supposed to be a floor that a lot of different apps can stand on.
A token with the rules on the coin
A KCC-20 token is a covenant. That’s a set of rules stuck to a Kaspa output, not a program living in a global account the way an Ethereum token does. The spec’s state is deliberately small. There’s an amount, an owner, scheme bytes that say how ownership and borrowing work, a borrow guard, and a 32-byte commitment if an app wants to hang extra data off the token.
A normal send has to keep the total token amount intact, and the owner has to authorize it. There’s a second path, borrowed receive, where someone can add tokens to a coin you already hold without your signature. They can’t take your tokens, change the owner, or drain the KAS sitting on that output. They can change the outpoint. If your wallet had an unconfirmed spend of the old one, that spend is now aimed at a coin that doesn’t exist anymore. That’s the part wallet authors are going to feel first.
None of this changes how Kaspa orders blocks. KCCs are conventions for wallets, indexers and apps. They are not a consensus change. The Toccata upgrade is what put covenants on the base layer. KCC-20 is one attempt to stop every project inventing its own token shape on top of that.
People who used KRC-20 keep making the same point, and it’s a fair one. Those balances depended on an indexer deciding who owned what. KCC-20 is written so the covenant checks the rules. Whether the wallet in your pocket actually does that, instead of quietly trusting an indexer again, is the test that matters.
Testnet talk, and a price that didn’t care
A launchpad account, Kasseal, said on October 14 that its KCC-20 launchpad is live on testnet and that mainnet is “soon.” Take that as their claim. The spec still points developers at a reference implementation for testing, and the Kaspa account asked people to try to break it. Nothing in the standards repository says a finished KCC-20 token is live on mainnet.
KAS didn’t react. On CoinGecko at 16:42 UTC, Kaspa was $0.03746, down 2.25% on the day, after a range of $0.03694 to $0.03915. Market cap was about $1.039 billion. Volume was about $11.7 million. Rank 76. At the time of writing, the market is treating this like plumbing.
That’s the right read until a wallet you already use shows a KCC-20 balance that doesn’t depend on somebody else’s server. The other thing to watch is that missing date on the header. A last call with no end date can sit there while everyone talks as if it’s almost done.