KAS (KAS)

For more K-Force ideas go here - https://t.co/xPQRwK28Yj https://t.co/m1u15qmPaq

In the same way many, if not all, industries will be digitised and revolutionarised on the decentralised $KAS level-1 on top of internet @DiiDesertEnergy @KaspaKii https://t.co/wcljy3Ba3K

@Igra_Labs just published a breakdown of how its system handles MEV (Maximal Extractable Value). This write-up comes from questions they’ve been getting from builders, integrators, auditors, and exchanges evaluating the network. MEV (Maximal Extractable Value) -This is the profit someone can make by manipulating transaction order instead of simply processing transactions as they come in. Common examples: Front-running: jumping ahead of a known transaction Sandwiching: placing transactions before and after yours to extract value Oracle manipulation: influencing price feeds to trigger outcomes On networks like Ethereum and many single-operator L2s, these strategies are often reliable and repeatable. What Igra is actually doing Igra is designed to preserve the transaction ordering properties of Kaspa’s L1. That leads to a different environment: - No single sequencer controls ordering - Ordering comes from a decentralized #ProofofWork #blockDAG - Exact transaction placement is difficult to predict and enforce

@EliBenSasson a mindset of humility + synergy of parallel complementing efforts

Yes - directionally true, but it needs precision. vProgs are not live yet. The roadmap model is: Kaspa orders transactions and provides data availability on-chain, while program execution happens off-chain and the chain settles/verifies the result instead of every node re-executing every contract. So it is not just “Kaspa but EVM faster”. It is a deliberate trade-off toward verifiable off-chain computation anchored to L1. Caveat: current programmability is covenants and Based Apps. Full vProgs are the future composability direction, with the stronger L1-enshrined ZK verification piece coming later.

Our two heroes this week? Eliott Mea and Luke Dunshea. Eliott released a mathematically rigorous framework for price oracles on Kaspa, and Luke released several Kaspian tooling kits, ranging from devnet experiment results to a node resource study, as well as an update to Kaspa’s genesis path for pruned nodes and an updated fork for Liberated Potatoe. Moreover, we saw key third-party development across the Kaspa ecosystem. Read about it here! https://t.co/XDLRmzVImc

Rollups are one of the clearest examples of crypto becoming more powerful and more complicated at the same time. The basic idea is elegant: do more work off the base layer, then post proofs or claims back to a more secure chain. That can lower costs and raise throughput. But it also creates a messier world for users. More domains, more bridges, more waiting, more assumptions, more places where things can feel fragmented. That is why rollups did not "solve scaling" in some final sense. They changed the shape of the problem. And once the shape changed, people started looking again at whether better base-layer design still mattered. That is part of the world Kaspa enters.