Sprotonick

@Sprotonick

Cofounder/Head of Research @KASmediadotcom Previously: Listings Research Lead for @BinanceUS @UCBerkeley Alumni

San Francisco, CA

Joined May 2021

7.7K Following

7K Followers

2.6K Posts

Pinned Tweet

Sprotonick

@Sprotonick

over 2 years ago

The Savior is Coming! He’s Dressed in Digital Silver! I may be jumping the gun, but thoughts: as shown in a previous article, Kaspa solves the blockchain trilemma at the L1 level. However, once smart contracts are implemented, Kaspa can also make the L2 level more decentralized and secure. This is a big deal, and for some reason, no one is talking about it. Kaspa can accomplish this by adopting either (or both) of the two smart contract implementation options proposed by Yonatan: 1) smart contacts implemented via L2 roll-ups with sequencing and settlement done on Kaspa, or 2) Kaspa becomes a sequencer for L2 Roll-ups executing contracts on Ethereum. Every L2 roll-up (i.e., Arbitrum, Optimism, zkSync) utilizes a single, centralized sequencer to order transactions. It’s important to note that they don’t need to use a single sequencer; instead, it’s a choice. Let’s examine why: roll-ups, by definition, were initially meant to be an entity for executing transactions while using the sequencing and data availability of an L1. However, due to Ethereum’s inefficient and slow sequencing, it’s more convenient for L2s to run their own centralized sequencer. Moreover, Ethereum’s data availability is too expensive, which has caused modular DA layers with less than secure systems to form (such as Celestia utilizing PoS). Thus, Ethereum’s inefficiencies are spreading to realms beyond the L1 level and making those realms, too, inefficient. Even more so, this has caused a modularization of the crypto universe, fragmenting liquidity and decreasing composability. Implementing smart contact integration option 1 resolves the issues above for Kaspa only. PoW miners will function as sequencers according to the BlockDAG ordering rules of GHOSTDAG/DAGKNIGHT. Sequencing will be fast and efficient enough (up to 100 blocks per second with DAGKNIGHT) to use L2 roll-ups for execution only (as originally intended); thus, L2s executing onto Kaspa won’t need a centralized, single sequencer. Additionally, by adopting a blob-carrying (aka payload) mechanism, Kaspa can compete against Celestia or any other modular layers, reducing fragmentation. Implementing smart contract integration option 2, however, gets juicer. Kaspa will serve as a sequencing side-chain for Ethereum or any other L1, decentralizing any L2 platform for any L1s. Thus, any L1 could reap the decentralized ordering benefits of GHOSTDAG/DAGKNIGHT (solving L2 centralization) and the energy defense system behind PoW (or as Jason Lowery calls it, a nonlethal weapon defense system). This is game-changing as a commodity-like monetary premium will anchor equity-like monetary premiums (PoS protocols). Lastly, the asynchronous nature of DAGKNIGHT could function as a countermeasure to MEV, thus providing MEV resistance to any L1 using roll-ups. Kaspa could be the knight in shining armor to save the entire crypto universe. Kaspa, as an Ethereum side-chain (or for any L1), may leave a bad taste in the community’s mouth. Moreover, many may ask why Kaspa should be the savior of other platforms — why not just focus on Kaspa’s ecosystem? I understand and sympathize with both intuitions; however, saving the world means massive and consistent mining rewards, which is especially important for Kaspa’s economic security once block subsidies are gone. However, it’s hard to save the world until your own army, so to speak, is strong and autonomous enough — in this case, Kaspa’s network and ecosystem. Therefore, adopting option one first makes the most sense, and once Kaspa is ready, it can alleviate any bad taste by adopting option two and save the world.