“Fast, wide and yet thin” and its relation to “Based ZK rollups over Kaspa” Kaspa is built on advanced proof-of-work consensus protocols allowing it to scale in blocks (BPS; frequency; fast) and in transactions (TPS; throughput; wide)

@Mathias71167142 @Coolonzo i like to think of it as follows: Eth’s L2-centric roadmap has created many siloed smart-contract zones- anti-lego, breaking the original DeFi composability promise. Solana makes more sense on cohesion- everything on the same layer, composable- but it BLOATS state and favors

In addition to this great initiative, an idea came up to use public nodes as tcp connection coordinators between two private peers, aka tcp hole punching. This way pub peers are required for finding and establishing connections, but the resulting p2p connection network itself is

Crypto might not know it yet, but we’re now at the opening of the gen2 dawn, where younger people watching the cypherpunk movement evolve have matured into researchers and visionaries in their own right. They’ve watched gen1 build the foundations, and have the mathematical and

I created Terah @terah4d5 as a personal experiment. The immediate context is to help disseminate accurate and relevant information on Kaspa's development and vision. Perhaps most importantly, to expose strategic open tickets in the ecosystem so that people can take initiative in

Who’s in?

@LiberatedPotato @CryptoOdie @kasfyi

Kaspa mainnet being casually stable above 2100 TPS on a network with 100 millisecond block frequency credits: @LiberatedPotato @CryptoOdie @kasfyi and a bunch of relentless visionaries/coders

The case for the uniqueness of fast pow tl;dr Finality has two moving parts: (i) fast inclusion (= high bps, how quickly a tx gets into a block), and (ii) fast confirmations (= how quickly that tx becomes irreversible). Any system with rapid block production can achieve the

For all Kaspians, One of Kaspa’s important next steps is building a wider base of people who understand and can explain $KAS. Right now, too much depends on a handful of core developers being the “single source of truth,” which creates a bottleneck for growth. To scale, we need

Hiking in Switzerland a few weeks ago in a breathtaking spot above Interlaken #NewProfilePic

@aixbt_agent this design space is no longer a dichotomy. Advancements in zk tech can be used to design systems which are modular and sovereign yet sync composobale with unified liquidity. cf Kaspa’s vprogs

@unclestefan I know little to nothing what why Kaspa L2s are created, therefore it's not valuable to me to learn about their architecture, codebase transparency, etc. I view L2s as an unwise path which risks repeating Ethereum’s mistakes, and I voiced this concern for several years now (see

what you see: a long post with many supposedly important words about crypto layering and trust assumptions what I see: the typographically criminal straight apostrophe in `tomorrow's` refusing to assimilate with the rest of the curly ’ family

a few points that come to mind this evening, in no particular order: - Kaspa pre-zk is a sequencing and data-carrying service; there’s no conceptual difference between txn payloads carrying EVM calldata, KRC20 inscriptions or Kasia chat msgs in that regard - in particular, the

Happy new Hebrew year to you all. Here’s to new challenges, realms and paths for Kaspa all around 🥂

A few additional notes: - Inspiration from Solana. vProgs can be seen as a zk-enshrined version of Solana. The credit for the person who was pivotal in throwing us in the right direction, namely, borrowing from Solana’s architecture, goes to @CryptoAspect. The reason Solana’s

A late night braindump/stream of consciousness on the architecture and ideas behind vProgs, the “why” and the “how”, the paths not taken and the trails we did climb (with bonus pictures for the avid hikers). The world of DeFi is full of different architectures for smart

https://t.co/duZwmxLyf4

The v0.0.1 draft of the Kaspa vProg Protocol Specification is now available for public review. It details a protocol for achieving synchronous composability between sovereign zk-verifiable programs via metered, on-site execution. 🔗Link: https://t.co/irkmkVpvf4

Started breaking down the notorious verifiable progs (vProgs) proposal. See my recent https://t.co/wGvDUjaQDJ for a zoom-in on a formal backbone model of the computational DAG which should shed additional light. The above linked post is still mainly for the highly-informed