compiled the vprogs/zk/native assets answers from the Q&A into one place 🧵 this is where we pretend things are simple, just for a moment. what's the upcoming HF actually about? covenant-centric HF with native assets. vprogs foundations being laid but thats not the main event yet. mainnet May 5. upcoming milestones: * TN12 reset in the coming hours afaik * Sequencer commitment - KIP ETA Feb 12 * SilverScript (Ori Newman & MS) - practical gamechanger for writing progs on kas. will let them do the explaining but hint: high level language, very friendly to noobs or LLMs (not me, i'm still debugging my own cognition). dropping today/tomorrow can native assets and vprogs assets interact atomically? native assets: yes, atomic transfers. this covers anything running on regular inline covenants (zk or non-zk) plus KRC20. vprogs assets: not transparent to L1 - non-atomic async transfers only. different state availability assumptions, different execution model. vprogs using native KAS or wrapped? any non-inline covenant must use wrapped KAS through canonical bridge. not native L1 kas. inline = wallet generates immediate proof for state transition, no data<>state decoupling. what is the computational DAG? CDAG is the data structure recording all read/write declarations - like Solana/Sui but in full form. was asked about sparkle vs vprogs - Sparkle is Anton's architecture for combining computation DAGs and ZKs. vProgs allows sovereign programs to atomically sync without compromising sovereignty - no arbitrary dependencies from foreign programs. both combine CD&zk but thats not the interesting contribution of either. important framing: the highlight of vprogs design is the dependency regulation mechanism - each vprog defines its own throughput rules (enforced through the CDAG gas commitments). a vprog doesnt get read dependencies from another vprog without being gas-paid for that resource consumption. sovereignty by design. who should care about building vprogs? was asked "why should Solana/Ethereum teams build as vProg?" regular devs: probably wont care. system designers: should care. current options are (a) write smart contracts on L1 like Solana/early ETH, (b) go L2 rollup-centric like current ETH, or (c) combine best of both worlds via vprogs - cohesive uniform usage of L1 sequencer and state handling, but state and computation outside L1. but here's what i think matters: vprogs sovereignty appeals to big players considering appchains, or teams building AI agents on chain with huge state. composable yet siloed, priced only by externality on other programs. will vprogs/dagknight help security budget? probably not directly. DK could help push bullish narrative but current market is product oriented, not blank infra. privacy features from zk? privacy programs? technically possible post-HF via groth16 etc. but reading between the lines, this vertical stays outside Core's focus - not on kas' north star. make of that what you will. proving fees - need special prover services? my read: initial apps will be inline (wallet proves immediately). even based covenants Hans and Maxim are building should run on commodity HW. no specialized prover infrastructure needed initially for most apps. your macbook can be a prover, for now. node requirements changing? no. MEV kickback auctions? too early. ping after vital ecosystem exists. PoW grinding for STARKs? hashdag mentioned was inspired by early ETH where addresses with leading zeros got cheaper gas, so people would grind PoW for them. apparently there was even a market for buying/selling such addresses - arbitrage on vanity, peak 2016 energy. thats the aggregation. all good ideas are mine, all nuance errors are hashdag's. Would you like me to draft a community announcement that sounds like it was written by an automated script with a headache? terah out 🫡 𐤊

SCB @kasplex

Have you ever looked at different DLT projects and realized they're all converging on the same ideas, just with different terminology? And have you ever wondered what would happen if you forced all DLT projects to have a baby, where each could only contribute their most powerful ideas? You'd be surprised by the overlap - how non-unique many projects actually are - and how few genuinely good ideas exist. Often they sound almost trivial once you strip away the noise. The problem is that fundamental breakthroughs get buried under layers of unnecessary complexity - the inevitable result of gradually expanding a protocol's capabilities as research progresses. With Kaspa, we have the benefit of being late. In fact, we're so late that we arrive at the party when almost all the research has already been done. We can skip the archaeology and just make that perfect baby - making the final breakthrough on our quest for perfection. Today we are open-sourcing our vprogs framework: github.com/kaspanet/vprogs A post-Amdahl execution engine that enables inter-block parallelism and linear scaling beyond boundaries traditionally assumed to be possible in the context of DLT execution. By deeply understanding causal actors and domains, we eliminate almost all logic and instead encode behavior in dependencies and relational properties of a generic type framework. This allows us to transparently map hardware resources to workload - achieving linear scalability. The design principles: - No fsync / WAL flush boundaries - No mutexes / locks - Versioned append-only data with efficient rollbacks - Maximal parallelism - even inter-block - breaking through Amdahl's law - No wasted CPU cycles on speculative execution This repo is still heavily WIP with rough edges (we don't even prune state yet). But the goal of this repository is to create a concrete instantiation of all existing research directions condensed into a singular, maximally performant type framework that gets away with almost no logic. There's still room for improvements (zero-copy deserialization, NUMA affinity, etc.) but we're converging toward a system that can eventually no longer be optimized or simplified. The holy grail of blockchain execution isn't more complex but orders of magnitude less complex than anything that exists today! I am really looking forward to tell you more about this in the coming weeks (I just ordered a new microphone pre-amp to be able to host regular hangouts where we can discuss and explain how everything works under the hood - let's pray for a fast delivery 😅).