Kwik𐤊

🚨 NEW Episode w @michaelsuttonil vProgs MasterClass (MUST WATCH) Full Youtube - youtu.be/xHlOcR1x2tU CC @hashdag @FreshAir08 In this exclusive 90-minute deep-dive, Ankit sits down with @michaelsuttonil, Co-Author of #KASPA #vProgs, for the most comprehensive explanation of vProgs (Verifiable Programs) to date. This isn't just another crypto interview - it's a masterclass in next-generation blockchain architecture. This is the conversation that will define how we think about blockchain scalability, liquidity fragmentation, and the future of decentralized applications. vProgs represent #Kaspa's answer to what many consider blockchain's greatest unsolved problem: the fragmentation crisis. While Ethereum's rollups trap developers and users in isolated silos (Base, Arbitrum, Optimism), vProgs create a unified, one-dimensional space where programs can synchronously compose while maintaining sovereignty. @michaelsuttonil breaks down complex concepts like #basedrollups, canonical ordering, #computationalDAGs, and #synchronouscomposability into understandable explanations. Whether you're a developer evaluating blockchain platforms, a researcher studying L2 solutions, or an investor trying to understand #Kaspa's technological edge, this episode provides the clarity you need. What makes vProgs revolutionary? Unlike traditional L2s that require trust assumptions and complex bridging, vProgs inherit L1 security directly, eliminate censorship risks, and create true unified liquidity through atomic composability. The experience? As Michael explains, it should feel "as if programs are on L1" despite executing off-chain with ZK proof verification. TOPICS DISCUSSED: vProgs Fundamentals - What they are and why they're called "verifiable programs" instead of smart contracts Single Sequencer Architecture - How Kaspa L1 enables synchronous composability that fragmented L2s cannot achieve. Based Rollups Superiority - Why having all roles on L1 eliminates trust assumptions and inherits full security Ethereum's Fragmentation Problem - The "failure supernova" that inspired Kaspa to design differently from day one One vs Two-Dimensional Liquidity - Why current L2s trap users in bundles and how Vprogs solve this Unified Liquidity & Asset Hubs - Creating a single liquidity space without bridges or fragmentation L1 Experience on L2 - How atomic composability makes off-chain execution feel native• Multiple VM Support - Supporting different virtual machines (Solana-style, EVM-adapted) as templates Validity Proofs vs Zero-Knowledge - Clarifying the cryptographic architecture behind vProgs Sovereignty + Composability - Balancing program independence with seamless communication ComputationalDAG - The breakthrough that made the entire vision click into place -------------------- This video is for educational purposes only and not financial advice. Always conduct your own research before engaging with blockchain projects or investments. #vProgs #kaspa #kaspa #kaspacurrency #kaspaupdates #kaspaecosystem #kaspanews

The article In which it was never my choice to hold the fire we found* written by @hashdag contained some development targets for Kaspa. "40–25 milliseconds targeted for the DK HF, benchmark pending; hopefully vprogs v2 is ready by then. Target date end of Q3'26." "10 milliseconds (100 bps) would likely require some dag algorithmic adjustments re how miners reference dag tips, in addition to further node perf optimizations, targeted for 2027 HF. Towards this HF, I hope to mature ideas around netsplit-resistance consensus." All Kaspa core development conversations can be publicly found here: t.me/kasparnd Read the rest of the article below! @hashdag/in-which-it-was-never-my-choice-to-hold-the-fire-we-found-937314149402" target="_blank" rel="nofollow noopener">medium.com/@hashdag/in-wh…

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

@picaye @hus_qy For cov++? ~40-50 days to fully-featured mainnet-ready testnet. A timeline will be announced as soon as possible

It’s exciting to see ideas that started as research and diagrams begin to materialize in real code. About a year ago, this research post laid out a design for based zk systems over Kaspa. Today, @Max143672 is implementing that scheme on top of zk opcodes built by @asaefstroem. See recent core r&d recap: t.me/kasparnd/1/101… The order here matters. We first designed the based zk building blocks, then mapped out the full vprogs architecture with sync composability in mind. Only with that end state clear does it make sense to start implementing the initial system. This way, even the first steps are already aligned with what comes next.