Kaspa Fees Debate Is Heating Up Fast

Hey, welcome to Kaspa Daily Pulse – here’s what the Kaspa community’s been buzzing about today.

First up… Warpcore. Folks were saying “Kii released Warpcore,” but the vibe got weird fast because people couldn’t find a GitHub link, and some were like, “so… is this ever going open source?” Others ran into a 404 link and the chat immediately went into skeptical mode. The core debate: is Warpcore actually meaningful for Kaspa, or is it basically just a “glorified audit log” that doesn’t create real demand for KAS? One side was like, “if it gets real companies settling on KAS, who cares, get them in.” The other side was like, “cool story… but where’s the fee pressure?”

Which leads into the spiciest nerd fight of the day: how fees really form. There was a legit back-and-forth on whether fees rise just from raw transaction volume, or whether you need competition and urgency—people racing to get included because being late actually costs them. Someone pointed to the “Rothschild” test and said fees started rising around two thousand TPS, while others pushed back hard: “volume alone doesn’t do it… contention does.” That convo also spilled into long-term security talk—subsidy pays miners today, but later on fees have to carry more weight, and “empty blocks” aren’t the enemy… low miner revenue is.

On the community-building side, there was hype around a Kaspa hackathon turnout. People were sweating not hitting two hundred hackers, but also admitting one hundred fifty is still solid—especially with minimal help—while comparing it to Ethereum pulling “two to three hundred” with way more marketing, and Solana doing “one thousand” with a massive prize pool. Net vibe: “we don’t have much… and still showed up.”

Then there’s protocol direction: talk in “hf chat” about native asset fragmentation and whether to delay the hardfork until vprogs are ready. People worried multiple versions of “the same token” could get messy from a wallet standpoint, and there’s a split between “let users do what they want” versus “don’t create chaos.”

Finally, small but real: Kaspa Social product friction. Users were asking for a proper “thumbnail/link preview,” someone explained the usual Open Graph approach… and a dev basically said, “yeah, our app doesn’t use Open Graph.” So: polish is on the radar, but not solved yet.

That’s it for today’s pulse. Let’s see what tomorrow brings. Catch you then.