David Perlo

[David Perlo @DavidPerlook]

@MZora0419 IA

[David Perlo @DavidPerlook]

@Arden_2210 34

[David Perlo @DavidPerlook]

#NuevaFotoDePerfil

[David Perlo @DavidPerlook]

@BSCGemsAlert kaspa

[David Perlo @DavidPerlook]

@cryptocom kas vs all coins

[David Perlo @DavidPerlook]

@DesheShai @Dohmer_ entonces no publiques más en x y desaparece, nadie puede romper o arruinar lo que no ve y conoce

[David Perlo @DavidPerlook]

@prex_tim @realvijayk kaspa hace todo lo que hace bitcoin. pero 1 millón de veces más rápido

[David Perlo @DavidPerlook]

@KaspaBuilders @VitalikButerin @hashdag @cz_binance @gavofyork b

[David Perlo @DavidPerlook]

@DesheShai me cuesta respetar comentarios de personas que abandonan el barco como rata y después siguen tirando piedras desde la costa.
Tampoco está bien que se hable mal de gente que no hizo lo que dicen que hizo, pero cuando el río suena es porque trae agua.

[Yonatan Sompolinsky @hashdag]

# dear @terah4d5,

when promoting vprogs, the following ingredients which are part of its design do NOT constitute the main contributions:

---

## List of non-contributions of vprogs architecture and yellow paper

1. use of computation DAGs to represent the underlying account state layer.
2. projection of zk tech onto Solana’s scalable, parallelism-friendly account-program architecture.
3. implementation of atomic composability.

**reason and context:** these ingredients merely create a Solana-like high performance yet monolithic L2 which does not provide app builders with the necessary autonomy and sovereignty. it is admittedly a step forward, definitely better than a monolithic L1, but still does not offer a fundamentally distinct product that addresses the shortcomings of existing L1 and retains teams within the base layer.

---

## Promote the notion of app sovereignty

emphasize instead following contribution of the vprog yellow paper:

**unique single contribution of vprogs:**
4. a per-vprog resource regulation mechanism that enables a layer of synchronously composable programs and which maintains the sovereignty of individual vprogs.

---

## Definition of sovereignty

### Dapp/vprog nodes can:
1. set their own throughput regulation parameters and prover incentives,
2. confirm txns immediately in O(consensus-latency) rather than O(proof-latency), even after composable interactions, regardless of other vprogs’ prover liveness, incentive sufficiency, or state size.

### Trust assumptions:
1. nodes assumed to trust the occasional liveness (=ability to prove and communicate with L1 in reasonable timeframes) of the **permissionless** set of provers of their own program, and to be pessimistically agnostic to those of other programs.
2. in the optimistic case provers of other vprogs are active and collaborative, and this smooths operation for all provers.
3. yet soundness does not depend on the optimistic route, and each vprog can ensure that the set of its dependencies is feasibly provable (=in terms of execution and proof complexity) and technically provable (=zkVM type is standard; prog code is available) by its own permissionless set of assumed-to-be-live provers.

---

## What happens when sovereignty is not prioritized

builders of high volume apps take off to their own sequencers or app-chains (Cf. Base, Unichain, Stripe), and fragment the ecosystem.

### Advanced discussion on sovereignty and the considerations of high profile defi teams

typical considerations when migrating off their home L1:

1. **latency** - solved with Kaspa Crescendo.
2. **fees** - computation-gas fees and, crucially, state-size fees are solved by vprogs: each program can define its own gas regulation and state-size STORM params; in contrast, data availability aka block-space fees are not solved, and should these become a primary bottleneck this will be addressed separately.
3. **MEV capture** - inherently unsolvable in the case of teams that insist on self-capturing their users’ MEV, and solvable via reverse MEV auctions in the case of teams that merely wish to prevent L1 miners from capturing it.

---

## Strategic implication for Kaspa

position it as the only L1 that designs for dapp sovereignty; attract activity from high profile teams / high volume defi projects that currently take off to their own siloed chains and sequencers due to L1 shortcomings and prescriptiveness; offer kaspa as dapp-sovereignty optimized sequencer

---

## Concluding description of Kaspa's enshrined vprogs layer

1. an asset-centric layer of sync-composable apps (vprogs).
2. borrows heavily from Solana's account-centric architecture, crucially adds cross-program gas regulation.
3. preserves dapp sovereignty by allowing each dapp to configure its zk stack and set its own throughput and state growth limitations.
4. stack includes zk verification opcode which enables both the throttling of cross prog dependencies and a canonical L1<>L2 bridge; imposes on L1 nodes minimal skeleton-related supporting ops.

---

## Tracking (timeline | contributions | tasks)
1. timeline heavily depends on num of developers chiming in and joining the efforts.
2. track your X account and the public rnd TG channel https://t.co/YwHTtTw0kh to learn about devs interested in contributing.

3. track X account of current main code contributor @hus_qy for more details on the Rust orchestrator.
4. report on projected timeline once you obtain some clarity on developer engagement and availability.
https://t.co/jV7QRaXGlL

cc
@CryptoAspect @michaelsuttonil @FreshAir08 @hus_qy @elldeeone

[David Perlo @DavidPerlook]

@BSCGemsAlert $kaspa

[David Perlo @DavidPerlook]

@Ashcryptoreal kaspa

[David Perlo @DavidPerlook]

@Ashcryptoreal Kas

[David Perlo @DavidPerlook]

@NoVive_Socialis Está bien, mueren ahí adentro porque ahí adentro están los delincuentes, peor en Argentina que mueren fuera de la cárcel personas inocentes, matados por algunos que deberían estar ahí adentro

[David Perlo @DavidPerlook]

@healthy_pockets No te olvides del inminente lanzamiento de KASPA en binance

[David Perlo @DavidPerlook]

@KASPAEnthusiast Mínimo 100 us

[CryptoManiac 🇸🇦 @CrypttoManiac_]

La campaña de marketing que Binance está realizando a Kaspa es impresionante, una de las mejores que he visto.

Hace unos días publicaron contenido sobre el trilema de escalabilidad, seguridad y descentralización, que Kaspa resuelve mediante su consenso GhostDAG.

Más tarde, subieron una foto mostrando un bloque con una estructura lineal, que luego borraron para reemplazarla por una imagen que representaba una cadena de bloques en paralelo, justo como lo hace Kaspa.

Ahora han compartido un post que dice:

Imagina retroceder en el tiempo para ser uno de los primeros en adoptar las grandes tecnologías, y si te dijéramos… aún es temprano?

Lo que interpreto de esto es que nos están diciendo que hay una tecnología revolucionaria, algo comprable a haber invertido en Bitcoin en sus inicios, pero que aún tienes la oportunidad de hacerlo ahora.

Es como una segunda oportunidad para aquellos que no invirtieron en Bitcoin en su fase inicial.

Invertir en Kaspa ahora es como haber comprando Bitcoin a $100.

Creo que es fundamental incluir $KAS en una cartera diversificada.

Nunca había visto una campaña de Binance tan agresiva.

[David Perlo @DavidPerlook]

@Grayscale K A S P A

[David Perlo @DavidPerlook]

@Grayscale Kas

[David Perlo @DavidPerlook]

@Aliciamaria62 @neuevolkisch @Trumperizar Claro por algo las matan señora así es…