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 😅).
