Kasplex @kasplex

Update on the KRC20 incident: The code repository has been updated: github.com/kasplex/go-krc… If you are running your own node, please upgrade: github.com/kasplex/go-krc… Stop the node process (or Docker container), delete the data directory, and restart the node; it will then automatically begin syncing.

Update on the KRC20 incident: Public APIs have been restored, and final checks to screen for anomalous transactions are currently underway. A code fix update for the go-krc20d repository will be released this week.

Update on the KRC20 incident: The full data revert process is currently 90% complete, and no consistency errors have been encountered so far. Once final verification is complete and successful, the latest version of the code and the docker-image will be released on GitHub.

Update on the KRC20 incident: The full revert and verification processes are proceeding smoothly; based on current progress, completion will still take several days. Once finished, the public API will be reopened, and further investigations will be conducted into the chains of transactions linked to the exploit.

KRC20 Incident Update: A vulnerability in the underlying protocol has been confirmed. Code-level fixes are complete, and a hard fork will follow. A full-state revert verification must be completed prior to the hard fork; this process is expected to take 3–5 days. Public node APIs will be disabled during this period; please do not perform any KRC20 token operations (such as transfers). For self-hosted nodes, please wait for the release of the new "go-krc20d" version before upgrading.

Regarding the recently discovered attacks on the KRC20 underlying protocol, we are conducting a detailed technical analysis and expect to provide further conclusions within 24 hours at the earliest. The public API will be temporarily disabled. During this period, please suspend all KRC20-related operations (such as transfers).

A few developer-facing Kaspa updates: - sources tell me Silverscript’s audit, and hence its first release, is nearing completion - Argent has a new home: github.com/orgs/argent-la… - Argent has grown up significantly since my last report: - route planning and related graph algos - cross-app linking - compiler-model consolidation - a unified, simple and intuitive runtime tx-construction API - and many, many more improvements and fixes - demo apps now range from the most elementary counter-state example, through a full DEX demo, to chess Chess was fully ported from the manual-routing implementation that originally inspired Argent to an equivalent automatically generated routing system, completely hidden from the dev/user. Each move is verified through L1 scripts with bounded onchain script cost (<5 KB). I’m also preparing the first short video episode, showcasing live end-to-end coding of a simple multi-actor Argent app.

📢 @kasplex Network Update Over the past month: • 29,461 new transactions • 950 average daily transactions • 28,437 cumulative transaction growth Over the past three months: • 100,632 new transactions • 1,094 average daily transactions • 99,562 cumulative transaction growth Not every phase of ecosystem development is immediately visible on-chain. Behind the numbers, @kasplex continues to improve its infrastructure, support new applications, and prepare the foundation for the next stage of ecosystem activity. Check: explorer.kasplex.org/stats

Crypto gave individuals sovereignty. Staghunt is betting the next frontier is the group version: coordination markets. Read more at our latest thought leadership in partnership with @hashdag coindesk.com/sponsored-cont…

Now that we have programmability paths on Kaspa, the need to converge on ecosystem standards in the right way becomes paramount. It appears we lack a fitting forum for such discussions. A primary and timely example would be a standard specification for native assets. We need a place for technical discussions where wallet devs, explorer devs, community thinkers, and core devs can brainstorm and rapidly converge on ideas without communication gaps, and without important ideas and messages getting lost to oblivion. As a start, here is a call for community discussion on native assets. An initial discussion on kas pub rnd is linked below, but again, to me this feels like an echo chamber, with probably the most important voices missing. >>

📣 Community Update: Latest network metrics for @kasplex EVM L2: • 31,652 new transactions • 1,021 average daily transactions • 30,671 cumulative transaction growth Over the past 3 months: • 112,317 new transactions • 1,221 average daily transactions • 111,031 cumulative transaction growth Network growth is only one part of the story. Our focus remains on expanding the Kasplex ecosystem with better infrastructure, more applications, and a stronger developer community. Check stats: explorer.kasplex.org/stats

my timeline organically filled with 4 different kas core dev updates is something I’ve dreamed of for a while

📢 Reporting to community: Over the past month, @kasplex EVM L2 has recorded the following on-chain activity: • 35,379 new transactions • 1,141 average daily transactions • 34,193 cumulative transaction growth Over the past 3 months: • 133,326 new transactions • 1,449 average daily transactions • 122,551 cumulative transaction growth The latest data shows that @kasplex is maintaining steady network activity, reflecting continued user interaction and a gradually strengthening on-chain base. Check stats: explorer.kasplex.org/stats

$KAS The Toccata Hard Fork is now live! Update your nodes well before June 30th so that you can remain in consensus! github.com/kaspanet/rusty…

Tomorrow it's finally time for the first community hangout! Kaspa Under the Hood: Setting the Stage for vProgs Grab a beer, coffee, tea, or whatever keeps you going, and join us for the first regular Kaspa community hangout. We will start with a high-level presentation of the upcoming vProgs architecture and Kaspa’s next stages of development. Since the architecture is extensive, this first session is meant to set the stage for future deep dives. The presentation is meant to be accessible to people with different technical backgrounds. We will take things step by step, build up the necessary context, and gradually develop a shared understanding of Kaspa’s architecture, trade-offs, and long-term vision. After that, we will move into a relaxed open discussion where people can ask questions, share ideas, and talk about anything interesting: Kaspa, decentralized infrastructure, incentives, technology, philosophy, or the future of humanity. Bring your ideas and questions, grab a drink, and join the conversation! discord.com/events/5991532…

Hans Moog @hus_qy

5 months ago

That's a really good question, but it's hard to answer in a single tweet because our mission is quite extensive, and it requires a lot of background knowledge to really understand what sets Kaspa apart. Currently, a lot of people see Kaspa as “Bitcoin’s crazy little brother”

51 303 733 86K 95

**Official Toccata Release — Mainnet Hardfork Activation Included** (Links in reply) We’re excited to announce the official Kaspa release containing the **Toccata Hardfork** activation logic. Toccata is scheduled to activate on mainnet at DAA score `474,165,565`, expected around **June 30, 2026, 16:15 UTC**. This is a consensus-changing upgrade. All node operators, miners, pools, exchanges, indexers, wallets, and infrastructure providers must upgrade before activation to remain compatible with the network. Toccata introduces a major expansion of Kaspa L1 capabilities, including: • **Native L1 covenant support** through transaction introspection, allowing for more expressive contracts, including stateful contracts • **Covenant IDs**, providing stable covenant lineage across UTXO transitions, so covenant instances can preserve continuity as their state moves from one UTXO to the next • **ZK proof verification on L1** via `OpZkPrecompile`, enabling to trustlessly offload computation off-chain. • **Partitioned sequencing commitments**, improving support for based ZK applications by making lane-local proving scale with relevant activity rather than global throughput Please upgrade as soon as possible and verify your nodes are running the new release well before the activation DAA score. Thank you to everyone who contributed to designing, implementing, reviewing, and testing Toccata.

Interesting idea! Turning the community’s enthusiasm for #Kaspa listing into visible, tradable market signals. Really looking forward to seeing it become reality! 🚀

JH @oneforonehaha

5 months ago

Kinda easy. In prior to the actual launch or coordination markets, I think the closest form is trading headlines on a prediction market such as: (1) #Kaspa will be listed on @binance in Oct/Nov/Dec 2026? Or NO in 2026? (4 options in total) The "community" can just contribute by

15 31 137 19K 11

Kaspa Toccata mainnet process update: Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing. Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today

Michael Sutton @michaelsuttonil

5 months ago

👀

32 158 625 89K 22

📢 Community Update: Over the past month, @kasplex EVM L2 has continued to maintain steady on-chain activity: • 36,816 new transactions • 1,188 average daily transactions • Peak daily volume reached 2,672 transactions Over the past 3 months: • 165,047 new transactions • 1,834 average daily transactions • 161,074 cumulative transaction growth The recent data shows that @kasplex continues to build a stable base of real network activity. Meanwhile, @kasplex infrastructure is also preparing for its next technical upgrade. As more applications, infrastructure tools, and ecosystem use cases continue to develop on @kasplex , the network is creating the foundation for the next stage of growth. Check stats: explorer.kasplex.org/stats

Something big is coming to the Kasplex infrastructure. ⛓️ We’re about to lower the barrier for decentralization, making it easier than ever for anyone to run their own node. Stay tuned for the technical upgrade soon!