上官謙 𐤊

The Kaspa Roadmap - What's Coming and When Most crypto roadmaps are vaporware. "Coming soon" means "maybe never." Kaspa's recent track record says otherwise. Already delivered: Crescendo upgrade (May 2025). Achieved 10 blocks per second with 100ms block times. Activated on schedule. Not delayed. Not broken. Just shipped. Coming Q1-Q2 2026: Covenants++ hard fork. Three main features: extended covenants for programmable spending rules, ZK proof verifier for trustless L2 integration, miner payload inspection for oracle infrastructure. Mainnet mid-2026 if testing goes smoothly. This is not the full programmability story. This is scaffolding. It enables L2 teams to integrate cleanly, lets developers experiment with covenants, gives R&D real-world feedback before vProgs ships. Coming 2026-2027: DAGKnight upgrade. Removes hardcoded consensus parameters, adapts to network conditions in real-time. Targets 100+ blocks per second, enabling 30,000+ transactions per second. This is the "broadband moment" for Kaspa. Coming 2026-2027: vProgs MVP. Off-chain execution with ZK proof verification, atomic composability through L1 computational DAG, Cairo VM for efficient proving (cost tied to execution steps not program size) . Gradual deployment with working versions that upgrade toward full design. Also planned: Reverse MEV auctions (miners compete to give users kickbacks instead of extracting value). Oracle voting (decentralized real-world data through miner attestation). ZK bridges for L1-L2 composability. Timeline credibility matters. The rust rewrite took longer than expected. Crescendo hit its May 2025 deadline. Current R&D under Yoni and Michael's leadership has matured. When they set timelines now, they mean them. This is not "check back in 5 years." This is iterative mainnet deployment with MVPs that work, learn, improve, upgrade. Real milestones. Real products. Real progress. Next in The Kaspa Blueprint Series: real-world use cases beyond speculation.

Kasplex L2: Final touches before Mainnet Smart Contracts on Kaspa deserve nothing less than perfection. That’s why, as we prepare for the launch of Kasplex L2, we’ve chosen to take a little extra time not because of bugs or technical blockers, but to ensure a flawless experience from day one. No bugs, just final touches The L2 is already fully functional. Core testing has confirmed that there are no critical issues or blockers under the lead designer @khriskang. However, as proposed by @5bb55b, we are adding an extra testing phase for deployment. These tests include: - assesing hardware environment requirement for major components such as stack, memory, storage, calldata, and counter - high availability deployment for each of the components - determine an adequate distributed system architecture - DR&BC mechanism for nodes, RPC, Relayer, and Explorer services This step will help us validate that client users and node runners will face no difficulties during the Kasplex EVM mainnet launch. When Kasplex L2 goes live, it must meet the highest standards of readiness, security, and user experience. What comes next Once the third-party testing phase is completed, mainnet can be activated at any time. Developers already in touch with us will be informed directly of the expected dates. In the meantime, here’s what the community can expect on the horizon: • [Event] Kaspa Experience in Berlin/Germany - 13th of September • [Event] Korea Onchain Symposium - 10th of September • Release of the roadmap for supporting L1 zkopcode and vProg – December 2025 • Launch of Kasplex LUA VM – introducing an "App Store" model for DApp builders on Kaspa Closing thoughts We know the community is eager, and so are we. But excellence takes time. By adding this final stage, we’re ensuring that Kasplex L2 not only launches but it launches strong, setting a new benchmark for smart contracts and scalability on #Kaspa. Thank you for your patience and trust. The wait will be worth it. The Kasplex Team

Two visions, one goal: smart contracts for Kaspa 1/4 – Intro With the arrival of smart contracts on #Kaspa, I wanted to better understand what exactly @Igra_Labs and @kasplex are building — and how it might shape the future of the ecosystem. I also have a few ideas for projects I’d like to build on Kaspa someday, so exploring these new tools helped me clarify what’s possible and for whom. Over the past few days, I dug into everything I could find — official docs, Reddit threads, Twitter posts, videos. I tried to answer a bunch of questions for myself: What is atomic composability? What makes a zk-rollup special? Why do we even need smart contracts? How does all of this affect developers, the Kaspa chain itself, and regular investors? One thing up front: this is not an “Igra vs Kasplex” post. The more I read, the more I realized these aren’t rival projects — they’re building toward different goals, with different philosophies and audiences. And maybe someday, they’ll even connect. I’m not a technical expert, so I probably misunderstood a few things. Please forgive any mistakes — and feel free to correct me! Still, I hope this thread helps someone else start exploring what smart contracts mean for Kaspa. Because for me, it took three full evenings and a lot of long reading sessions. #kasfam $KAS 👇

This one is special. RWA tokenisation, Supply chain and Commodity trading. A great test case… watch this space. Powered by Kaspa.

🦄How many Proof-of-Work projects are actually left in the top 100? Not many. Here’s the shortlist: ⚙️ Bitcoin ( $BTC) ⚙️ Litecoin ( $LTC) ⚙️ Dogecoin ( $DOGE) ⚙️ Kaspa ( $KAS) ⚙️ Bitcoin Cash ( $BCH) ⚙️ Ethereum Classic ( $ETC) That’s it. Out of 10,000+ coins, only a few PoW giants are still standing. But here’s the truth nobody tells you: 🧠 Bitcoin is too slow 💸 Litecoin is forgotten 🐶 Dogecoin is a meme 👴 Ethereum Classic is a ghost chain 🔄 Bitcoin Cash is just a fork 🚀 Kaspa is the only one: ✅ Fastest PoW ever ✅ BlockDAG tech (not just a chain) ✅ 1 block/sec finality in seconds ✅ Fair launch no VCs ✅ Active devs, growing ecosystem 📉 While others are living off hype or history, Kaspa is building the future of PoW. 💬 Are you still betting on old relics… or are you stacking $KAS before the world catches up?

60+ enterprise markets, each one ready for disruption by Kaspa Tech. We'll break down the industries, the standards they use now for management and settlement, what's broken, and how Kaspa Tech could replace them or fill in the gaps. Some of these initiatives are already in motion with @KaspaKii and others. Developers. Entrepreneurs. Take notice. Kaspa is becoming the ultimate decentralized, programmable settlement layer, and it's unlocking a new frontier of innovation and opportunity. Powered by #Kaspa. 4. Aerospace Legacy Standards (Global + NA based) • AS9100 (aerospace quality management) • DO-178C / DO-254 (software and hardware certs for avionics) • ITAR, EAR (compliance for sensitive technologies) • GS1, ATA Spec 2000 (traceability, logistics, parts interchange) • ISO 9120, NADCAP, FAA CFR (maintenance, parts handling, repair) AeroTech Systems & Platforms • Boeing/Airbus vendor networks • MRO software: Ramco, Trax, IFS Aerospace, AMOS • Digital thread tools: PTC Windchill, Siemens Teamcenter • Flight & maintenance data systems: Honeywell Forge, GE Aviation Digital IoT, Sensor & Telemetry Layers • Real-time aircraft diagnostics (engines, systems, avionics) • Maintenance & inspection logs • Parts lifecycle tracking (rotables, serialized inventory) • Flight hours, fuel efficiency, carbon reporting • Ground handling and supply chain logistics What’s Broken / Innovation Gaps • Legacy systems still rely on paperwork and PDFs • Flight-critical part traceability is fragmented • Delayed maintenance records increase risk and cost • Counterfeit or unauthorized parts in global channels • Carbon reporting is unverifiable • Complex MRO billing and disputes slow down cashflow • Security risks in centralized flight data systems Where Aerospace Can Still Innovate and Where Kaspa Fixes This Broken part traceability ❌ Vital aircraft parts often lack a complete digital history, especially after third-party repairs. ✅ Kaspa could anchor every maintenance and movement log on-chain, creating an unbroken digital thread. Outdated maintenance documentation ❌ Inspections, service, and certification data often live in siloed systems or PDFs. ✅ Kaspa could timestamp and secure maintenance events, allowing regulators and MROs instant validation. Counterfeit or gray-market components ❌ Subpar or unauthorized parts put lives at risk. ✅ Kaspa could verify origin and certification status of every serialized part using blockchain-based identity. Unverified carbon reporting ❌ Airlines struggle to prove emission offsets or fuel optimizations. ✅ Kaspa could validate fuel records, green routes, and emission cuts using real telemetry logs. Complex, delayed payments in MRO and logistics ❌ Work orders and supply payments are often stuck in manual reconciliation. ✅ Kaspa smart contracts could trigger instant payment when milestones are verified. Flight data centralization risk ❌ Airlines and OEMs house sensitive telemetry in central systems vulnerable to hacks. ✅ Kaspa offers a decentralized option for secure, verified flight data storage and access control.

🧵 1/10: Let's dive into what @KaspaKii (the Kaspa Industrial Initiative Foundation) is building. As a foundation dedicated to pushing Kaspa's blockDAG technology into industrial and enterprise applications, they're focusing on real-world utility in finance, energy, and beyond. Their mission? To make Kaspa the ultimate digital commodity for global transparency, speed, and security.

Thank you all for joining today’s speech about what Kasplex is. Sadly the livestream wasn’t provided in due time but we will post the recording very soon. We are proud and excited to announce our L2 launch mainnet date. This is possible thanks to the incredible work of our team who worked diligently for the last 6 months, non stop, no vacation, full dedication for what we believe in. We would like to say thank you to everyone who believes in Kaspa and its potential and we welcome all of you to explore it. The wait is over. Smart contracts on $kas via Kasplex L2 will happen on 👇 31st August 2025

🎉 1 Year of KaspaCom! 🎂 A huge thank you to the entire Kaspa community for an incredible year. Happy birthday to you! To celebrate, we're activating 2x points on all @YonatoshiNFT trades until 23.07! Together, we’re scaling Kaspa — For the community, by the community. ⚡️

感慨 $kas 生态的快速发展, #kaspa 的新项目和网站,我是完全追踪不过来了. 刚发现个网站 kaspaglo.be 统计并可视化了kas全球的所有peer, 1个peer基本可以理解为1个kas私有或公有节点. 节点总量21981个,可定位的是18496个节点,这数量远超我的预期. POS网络一般仅有几个到几百个节点.

Raw thoughts re Kaspa’s next big upgrade(s) You don’t end on a crescendo, and it is no secret that several anticipated upgrades are waiting on the sidelines for Kaspa. Primarily, the Dagknight (DK) protocol and the ZK L1<>L2 bridge. These two major endeavors may look independent, but I see strong merit in bundling them into a single hardfork (reasons below). I also argue this bundled effort is the right window to incorporate the foundational L1 changes needed to support ongoing research into MEV‑resistance and oracle‑voting. A word on deferring DK to this point. I acknowledge that per past statements we expected to be post‑DK by now. Context for the long delay: (1) after the Rust rewrite, moving from 1→10 bps (blocks/sec) was too natural a follow‑up to ignore, and I dove into ~1‑year of work there. (2) Strong community push for smart contracts; in the absence of formal committees planning the next phase we reasoned that prioritizing smart contract enablement would let a builder community form around the Kaspa app layer, and that unleashing this potential (and its ripple effects) would let us refocus on L1 perfection without bottlenecking ecosystem growth. This post provides a bird’s‑eye overview of active + upcoming Kaspa R&D efforts and sketches their relation graph. DK: Dagknight is a ’22 ordering‑protocol research paper by myself & @hashdag; it evolves GHOSTDAG (GD). A (mostly written) follow‑up post will deep‑dive DK across: - practical benefits / applications of its abstract “no a priori delay bound” property - a breakdown into four main components → raw development phases - broader system / consensus implications - applied research for efficient incremental algorithms (notably the cascade voting procedure) - protocol (and paper) relaxations / simplifications - “resistance to Internet chaos”: practical limits + engineering caveats ZK: In the past year, there has been an ongoing publicly visible effort to establish the landscape of ZK over Kaspa. The results of these efforts can mostly be viewed in Kaspa’s research forum under the L1<>L2 category. Kaspa’s approach is to support based ZK rollups, where “based” means the ZK layers / rollups / dapps fully commit to L1 sequencing—so L1 serves all three roles: sequencing, data availability, settlement. The base mechanisms to support this are largely established. The main area still under heavy research is atomic / synchronous composability (multi‑rollup transactions that land atomically). Explaining the vision and mapping current research there deserves its own dedicated post. Why bundle DK + ZK: Their technical complexities barely overlap, so development can proceed in parallel and merge cleanly. That’s the engineering case. There is also a safety case: we (strongly) conjecture DK yields faster practical convergence of total DAG ordering. Under normal operation the delta is likely inconsequential; under powerful attack attempts DK’s convergence could be much faster—possibly by orders of magnitude. Faster convergence of total order is especially valuable for smart‑contract systems that are highly order‑sensitive. This further strengthens the case for linking the two upgrades. Additional elements that should ship with them are support for reverse MEV auctions and oracle voting mechanisms (two of @hashdag’s ongoing research efforts with @yaish_aviv and @elimmea respectively; see his recent Sydney/HK talks), seizing the opportunity to address some of DeFi’s hardest problems using Kaspa’s unique structure. Once full smart contracts are live we will inevitably inherit the MEV + oracle weak spots seen elsewhere. By making a few minimal, high‑leverage consensus changes now, we can “apply the remedy before the blow”. Engineering cost here is negligible relative to DK + ZK while ecosystem upside is large. Here is how we can approach each: MEV. Proposed approach: reverse auctions in which miners offer kickbacks to users for transaction‑ordering (or bundle) rights. Kaspa’s parallel 10 bps DAG already produces intra‑round competition; formalizing a kickback path captures that value for users instead of private orderflow brokers. L1 requirements are small: add a canonical kickback route and a deterministic auction‑ordering rule in consensus (how to rank conflicting bids; details are still open afaik). Game‑theoretic refinements can follow post‑fork, but a base path should exist in my opinion. Oracles. The strategy for oracles is to leverage Kaspa’s high bps to enable a robust, real-time attestation network, with data aggregated from numerous miners each round. From an L1 perspective, the main consideration is whether to tie this system to PoW for greater security/sybil resistance. The practical step would be to add miner voting mechanics at the consensus level. This is a low-cost, preparatory change that provides significant future flexibility for L2 oracle designs. ————— Overall I expect dk/zk branches to begin landing soon in rk’s main repository. Looking forward to this turning into a beautiful decentralized open source coding voyage

KASmedia recently sat down with the team behind Igra Labs, Pavel and Dennis. We cover the overall future of L2 scaling, not just for Kaspa but for proof-of-work in general, particularly Bitcoin: from BIP-420 and fractional reserve banking to global sequencing solutions and based-rollups. This is an extremely important read! kasmedia.com/article/igra-l…

A random thought TL;DR: A Kaspa pre-ZK-based rollup/dapp can store only transactions targeting it plus a small fraction of all other txs and still prove correct execution. Full story: Say you’re building a based dapp¹ on current² Kaspa. Due to the lack of ZK-verification capabilities on L1, you would, supposedly, need to store all transaction data since the launch of your dapp in order to prove correct execution up to the current state (using the new sequencing commitments). Observation: Naively, you would need to store all L1 DAG txs—including native ones and those targeting other dapps—because for each tx you must show whether it targeted your dapp or not (i.e., you need to prove non-membership as well). Idea: Define valid dapp txs as those whose ID ends with 10 zero bits. For wallets/clients generating txs for your dapp, the cost will be merely 2¹⁰ Blake2b hashes on average—cheap. The payload simply includes a nonce you increment until the tx ID satisfies the condition. Result: You can now keep only the IDs for txs without a 10-bit suffix (because that itself is proof of non-membership) and the full tx data for those with the suffix. That translates to storing O(dapp-activity) plus approximately 1/1,000 of all other activity. Of course, the suffix length can be adjusted. Refinement: Instead of a suffix, choose a predetermined set of 10 bit positions (out of the 256 bits of each tx ID) to avoid strategy collisions with other dapps. Why I find this interesting: Because I’m thinking about a minimum-viable platform for developing and running dapps on Kaspa in the short term, getting closer to the order of magnitude of dapp-activity storage costs is crucial. ¹ Based dapp: a dapp using Kaspa’s L1 sequencing and data availability that tracks transactions containing payloads following some format and executes them on a predefined VM ² Post-Crescendo, pre-ZK era

The increasing frequency of withdrawal restrictions on centralized exchanges stems from Kaspa’s rapid emission schedule, which induces a perpetual state of tight on-exchange liquidity. Exchanges with the poorest accounting practices are exposed because they must impose the most stringent withdrawal restrictions. Unlike the traditional banking system, where new fiat currency can be created instantly through dubious accounting techniques, Kaspa is real (digital) commodity money: new Kaspa coins can only be created by mining on the network, and only in amounts predetermined by the protocol’s emission schedule. The emission schedule is virtually immutable because it can only be changed by a consensus among those who have a vested interest in never changing it. Centralized exchanges can temporarily mask their liquidity issues by limiting KAS withdrawals. Unfortunately for both them and their users, however, these problems will only worsen over time. Since new supply declines so rapidly, Kaspa’s on-exchange liquidity will remain perpetually constrained. Even exchanges with mostly sound accounting practices may face issues because any degree of settlement delay can create a mismatch between the exchange's Kaspa assets and liabilities. This stems from the fact that fiat currencies tend to depreciate so quickly relative to Kaspa, and thus accepting fiat currency without instantaneously increasing Kaspa reserves can create asset-liability mismatches over time. Additionally, since market participants using KAS as a store of value tends to grow so rapidly over time, exchanges face growing KAS withdrawal demand, which can rapidly transform asset-liability mismatches into liquidity shortfalls. Exchanges that are the most at-risk for a Kaspa liquidity event combine these three attributes: (1) extremely leveraged/margin cash- or stablecoin-settled Kaspa derivatives trading, (2) Kaspa spot trading, and (3) unrestricted Kaspa withdrawals. This trifecta, which occurred on CoinEx in February 2025, can create a liquidity event during periods of increased volatility: highly leveraged short derivatives traders can push Kaspa’s price far below what the spot market can possibly deliver to arbitrageurs and/or accumulators. In turn, allowing unrestricted Kaspa withdrawals could enable arbitrageurs and/or accumulators to drain an exchange’s primary KAS wallet almost completely within minutes. This is why CoinEx decided to end KAS/USDT margin trading several months ago. Over time, exchanges with questionable accounting practices will be forced to suspend KAS withdrawals indefinitely since they don’t have enough KAS to meet withdrawal demand. Indeed, liquidity constraints are the primary reason for them imposing frequent and arbitrary withdrawal limits. Although no centralized exchange conducts a full, public audit of its Kaspa assets and liabilities, Kaspa itself nonetheless exposes the exchanges with the greatest asset-liability mismatches. This is because the exchanges with the greatest shortfalls must impose the most withdrawal restrictions. We can conceptualize this situation as Kaspa effectively subjecting centralized exchanges to an audit—one that is the most reliable of all possible forms of an audit. All other forms of an audit are inherently some degree more trust-based and centralized, and thus more corruptible. Kaspa is therefore a decentralizing force the likes of which the world has never seen before. Kaspa is even more decentralizing than Bitcoin. Ultimately, no financial institution will be able to withstand Kaspa's decentralizing force.

We are actively working on advocacy and enablement for Kaspa with Industrial partners which is the core mission, along with hardcore R&D. We then have simultaneous work-streams for Kaspa ISO 20022 readiness, testing the WarpCore transactional middleware and engaging with regulatory authorities. Gigawatt Stablecoin is also under active development and again working the energy industry and regulatory agencies. And other commercial work that we won’t we speaking about publicly just yet. Just a reminder that we are an industrial initiative so we are focusing on enterprise solutions.

Why we won’t take over @KaspaCurrency We’re genuinely flattered by @xximpod’s recent proposal that KEF might manage Kaspa’s most visible comms channels. It’s a sign of trust—and we deeply appreciate that. But we have to kindly—and firmly—decline. Our role isn’t to represent Kaspa. It’s to support it. We believe in a decentralized, permissionless ecosystem where no one speaks for Kaspa. KEF’s mission is to pool resources, fund talent, and promote initiatives that help Kaspa grow—without becoming a voice of authority over the protocol itself. A vision shared by @hashdag. We’ll keep using @Kaspa_KEF to speak in our own voice. Not as gatekeepers, but as ecosystem stewards. If that resonates with you, we’d love for you to follow along and be part of the conversation. That said, we’re happy to amplify thoughtful messages that reflect Kaspa’s ethos—especially when they help newcomers understand what makes this ecosystem unique. Our goal is to contribute meaningfully, not to define the narrative.

🚨 Development Update 🚨 In preparation for our incentivized testnet, Zealous Swap smart contracts will enter audit this week with one of the most reputable firms in DeFi — they’ve audited many of the biggest protocols. We’ll reveal the name once it’s complete. We're also bringing in a local cybersecurity team to test our infrastructure over the next month. Full stress testing ahead. Security isn’t optional — it’s our priority. We’re building for scale. 🔥🔒

Today history was made! Congratulations to everyone who made this happen. You guys rock !

Congratulations to #Kaspa and the entire community on the successful Crescendo Hard Fork! We're excited to report that everything went smoothly on our end. Our KRC20 Nodes (2.0.3) have migrated seamlessly, and the four new OP codes, along with the rest of the protocol updates, are now fully live on Kasplex. A heartfelt thank you to everyone for your continued support and commitment to the Kaspa ecosystem. This is just the beginning!

Why Kaspa Outperforms Traditional Blockchain Solutions Addressing the critical needs of enterprise and industrial applications #kaspa $kas #Bitcoin