Skip to main content

Features

Kalypso is designed to be a key component of the proof supply chain. As a result, its architecture is versatile, making it easy to be integrated into any tech stack as a decentralized Infrastructure-as-a-Service.

A few of its architectural highlights are shared below:

  1. Modular: Kalypso’s modular design allows it to be plugged and played into any ZK application allowing developers to focus on their apps instead of infrastructure maintenance. As markets can be created for any circuit, the marketplace can also cater to developers building on different zkVMs. zkVMs allow developers to write code in familiar programming languages like Rust. Unlike applications that use custom circuits, applications built using the same zkVM can use the same orderbook allowing for a much less fragmented prover market.

  2. Composable: Protocols with their own proof networks (for eg. rollups) can also leverage Kalypso provers in their protocol as the network’s provers who stake the protocol’s proprietary token can still outsource proof generation to an open proof market for better cost efficiency.

  3. Parallelizable: In order to generate proofs faster, it might sometimes be desirable to break proofs of a large computation into parts or segments and then generate a proof of having verified the individual proofs to prove the whole. Of course, this is only possible when the computation is such that there are no dependencies between the segments. Similarly, for better liveness guarantees, some applications might want a higher degree of redundancy in case a prover fails to generate the proof within a specified time. Such distributed and parallel proving is as simple as placing multiple orders on Kalypso.

  4. Flexible: Kalypso uses a two-dimensional matching engine algorithm along the dimensions of time and price. Some applications and/or users are cost-sensitive while others more time-sensitive. When placing bids, Kalypso offers users the ability to state their preference on whether to prioritize time-to-proofs or cost. Accordingly, Kalypso matching engine ensures that the fastest machine with a price quote below the user’s price cap is chosen or the cheapest one with a response time below the user’s maximum response time limit.

  5. Extensible: Although Kalypso itself only offers low-level primitives, these primitives are powerful enough to build any sort of abstractions on. Apps can choose to pay on behalf of their users using meta-transactions. Others might enable subscription models while yet others may want to offer future markets to allow for predictable pricing and revenues. Such logic on how bids are submitted can be added at the SDK or application level and is easily compatible with Kalypso.