Difference between revisions of "Espresso Systems"

From CryptoWiki

(Created page with "e")
 
m
Line 1: Line 1:
e
From their [https://www.espressosys.com/blog/introducing-espresso-systems introduction] (7-3-2022):
 
''"Espresso Systems is developing Espresso: a [[Layer One|layer 1]] [[blockchain]] system that combines [[Proof-of-Stake (PoS)|proof-of-stake]] consensus and a [[Rollups|ZK-Rollup]] mechanism to achieve high throughput and low fees. Espresso has also developed Configurable Asset Privacy for [[Ethereum (ETH)|Ethereum]] (CAPE), an application that can run on any [[Ethereum Virtual Machine (EVM)|EVM]] blockchain (and will eventually run on Espresso natively). CAPE enables asset creators to offer users customized privacy guarantees."''
==Basics==
*Based in:
*Started in / Announced on:
*[[Testnet]] release:
*[[Mainnet]] release:
==History==
==Audits & Exploits==
*[[Bug bounty]] program can be found [insert here].
===Bugs/Exploits===
==Governance==
===Admin Keys===
===DAO===
===Treasury===
==Token==
===Launch===
 
* [https://docs.cape.tech/espresso-systems/cape-user-guide/requesting-additional-testnet-usdcape-tokens Will have] a CAPE token for their CAPE project, as can be seen on their [[testnet]] (6-2022).
 
===Token Allocation===
===Utility===
===Other Details===
==Coin Distribution==
==Technology==
*[[Whitepaper]] or docs can be found [https://docs.cape.tech/espresso-systems/ here].
*Code can be viewed [https://github.com/EspressoSystems/ here].
===Implementations===
*Built on: will be on its own [[Layer One|L1]], but hasn't so far (25-10-2022)
*Programming language used:
====Transaction Details====
*Capacity ([[TPS]]):
*[[Latency]]:
===How it works===
 
* From their [https://www.espressosys.com/blog/introducing-espresso-systems introduction] (7-3-2022):
 
''"What is needed is an approach that can maximize throughput while maintaining decentralized data availability. At Espresso Systems, we are developing a solution to this by tightly integrating the ZK-Rollup scaling mechanism with our proof-of-stake consensus protocol from the start. The fact that the Espresso ZK-Rollup is natively integrated with consensus—and does not need to treat it as a black box—is what will enable Espresso to avoid the trade-off of other designs which approach the rollup as a separate modular component agnostic to the underlying consensus protocol."''
 
===Fees===
===Upgrades===
===Staking===
====Validator Stats====
===Liquidity Mining===
===Scaling===
 
* From their [https://www.espressosys.com/blog/introducing-espresso-systems introduction] (7-3-2022):
 
''"Espresso’s approach to scaling throughput involves a careful integration of [[Zk-Rollup|ZK-Rollup]] for the [[EVM]] with a [[decentralized]] [[Proof-of-Stake (PoS)|proof-of-stake]] consensus protocol. A server aggregates a large number of [[Transaction (Tx)|transactions]] into a single summary transaction and produces a succinct zero-knowledge proof ([[Zk-SNARK's|zk-SNARK]]) of their validity, which is subsequently sent to the consensus system. This rollup proof compresses both the amount of information and the computation that the consensus protocol needs to validate the transactions, thus increasing the throughput."''
 
===Interoperability===
===Other Details===
==Oracle Method==
==Compliance==
 
* From their [https://www.espressosys.com/blog/introducing-espresso-systems introduction] (7-3-2022):
 
''"While CAPE can be used by anyone looking to create or [[Wrapped Tokens|wrap]] assets, the protocol was designed with [[Stablecoins|stablecoin]] providers specifically in mind. Stablecoin providers today generally want to maintain avenues to be able to address fraud, theft, and dispute resolution, demanding that they retain insights into the ledger of activity for their assets as well as controls like [https://www.espressosys.com/blog/viewing-and-freezing-with-cape freezing] capabilities. Prior to CAPE, there were no solutions for these types of asset creators to offer privacy-enabled versions of their tokens to users while being able to meet needs around visibility and dispute resolution. With CAPE’s viewing and freezing policies, this is now possible."''
 
==Their Other Projects==
 
=== Configurable Asset Privacy on Ethereum ===
 
* Got [https://www.espressosys.com/blog/start-using-cape-on-goerli-testnet released] on [[Goerli]] [[testnet]] (16-6-2022).
* From their [https://www.espressosys.com/blog/introducing-espresso-systems introduction] (7-3-2022):
 
''"CAPE (Configurable Asset Privacy for [[Ethereum (ETH)|Ethereum]]) is a [[Smart Contract (SC)|smart-contract]] application developed by Espresso Systems which enables digital asset creators to determine who can see what information about the activity in the [[Token|tokens]] they mint.''
 
''Digital assets on CAPE, from [[stablecoins]] to [[Non Fungible Tokens (NFTs)|NFTs]], can be customized to balance transparency, a noted benefit of [[Web3]] products, with privacy, wherever it is required by users. While CAPE transactions appear anonymous and indistinguishable to normal viewers, hiding even the type of asset being transacted, the creator of an asset can configure a viewing policy, which ensures that select parties can decrypt select information about transactions for that asset.''
 
''CAPE can be used to create new assets or to [[Wrapped Tokens|wrap]] assets that already exist on [[Ethereum (ETH)|Ethereum]], endowing them with privacy properties. Wrapping an [[ERC20 tokens|ERC-20]] with CAPE requires the specification of a wrapper type, which configures who can see what and who can maintain specific controls regarding the assets in question. Wrapping locks the asset in the ERC-20 contract and creates a corresponding CAPE asset of the specified type, while unwrapping burns the CAPE asset and releases the lock."''
 
=== Hyperplonk and their other Plonk implementations ===
 
* From their [https://www.espressosys.com/blog/hyperplonk-a-zk-proof-system-for-zkevms blog] (24-10-2022):
 
''"Over the past few years, [[Plonk]] has become the proof system of choice for most applications in the blockchain space. The reason is that Plonk provides great tradeoffs with short proofs, efficient verification, a high level of customization, and minimal trust assumptions. Unfortunately, Plonk still has limitations, especially when proving large statements or trying to use highly parallel hardware. These limitations are especially important when proving large and complex statements such as [[rollups]] and zkEVMs.''
 
''To overcome these bottlenecks, we built Hyperplonk. A new zk-proof system with a fully linear time prover and support for high-degree and lookup custom gates. Our prototype Hyperplonk implementation already beats our highly optimized Plonk implementation ([https://www.espressosys.com/blog/introducing-the-jellyfish-cryptography-library Jellyfish]), starting from circuits with about 16000 constraints, and the gap keeps growing as statement size increases or more parallelism is used. Hyperplonk also enables high-degree custom gates and lookup, something that is particularly useful for complicated circuits like the ZK-EVM one. These special gates can be used to enable complex [[Ethereum Virtual Machine (EVM)|EVM]] OPCODES and building a memory stack."''
 
==Roadmap==
*Can be found [Insert link here].
==Usage==
===Projects that use or built on it===
==Competition==
==Pros and Cons==
===Pros===
===Cons===
==Team, Funding and Partners==
===Team===
*Full team can be found [https://www.espressosys.com/about here] (25-10-2022).
===Funding===
 
* Mentions the following investors on their [https://www.espressosys.com/about#s4 website] (25-10-2022):
 
[[Greylock]], [[Electric Capital]], [[Polychain Capital]], [[Scalar Capital]], [[Sequoia Capital|Sequioia]], [[Paxos]], [[Gemini]], [[Robot Ventures]], [[Blockchain Capital]], [[Coinbase (COIN)|Coinbase Ventures]], SLOW, ZKV, [[Alameda Research]]
 
===Partners===
==(:==
Knowledge empowers all and will help us get closer to the [[decentralised|decentralized]] world we all want to live in!
 
Making these free wiki pages is fun but takes a lot of effort and time.
 
If you have enjoyed reading, tips are appreciated :) This will help us to [[keep]] expanding this archive of information.
 
[[ETH]] tip [[address]]: 0x83460bE5F218b1520B69D702cE60A1DE37dD8E31
[[Category:Companies/Organisations]]

Revision as of 10:04, 25 October 2022

From their introduction (7-3-2022):

"Espresso Systems is developing Espresso: a layer 1 blockchain system that combines proof-of-stake consensus and a ZK-Rollup mechanism to achieve high throughput and low fees. Espresso has also developed Configurable Asset Privacy for Ethereum (CAPE), an application that can run on any EVM blockchain (and will eventually run on Espresso natively). CAPE enables asset creators to offer users customized privacy guarantees."

Basics

  • Based in:
  • Started in / Announced on:
  • Testnet release:
  • Mainnet release:

History

Audits & Exploits

Bugs/Exploits

Governance

Admin Keys

DAO

Treasury

Token

Launch

  • Will have a CAPE token for their CAPE project, as can be seen on their testnet (6-2022).

Token Allocation

Utility

Other Details

Coin Distribution

Technology

Implementations

  • Built on: will be on its own L1, but hasn't so far (25-10-2022)
  • Programming language used:

Transaction Details

How it works

"What is needed is an approach that can maximize throughput while maintaining decentralized data availability. At Espresso Systems, we are developing a solution to this by tightly integrating the ZK-Rollup scaling mechanism with our proof-of-stake consensus protocol from the start. The fact that the Espresso ZK-Rollup is natively integrated with consensus—and does not need to treat it as a black box—is what will enable Espresso to avoid the trade-off of other designs which approach the rollup as a separate modular component agnostic to the underlying consensus protocol."

Fees

Upgrades

Staking

Validator Stats

Liquidity Mining

Scaling

"Espresso’s approach to scaling throughput involves a careful integration of ZK-Rollup for the EVM with a decentralized proof-of-stake consensus protocol. A server aggregates a large number of transactions into a single summary transaction and produces a succinct zero-knowledge proof (zk-SNARK) of their validity, which is subsequently sent to the consensus system. This rollup proof compresses both the amount of information and the computation that the consensus protocol needs to validate the transactions, thus increasing the throughput."

Interoperability

Other Details

Oracle Method

Compliance

"While CAPE can be used by anyone looking to create or wrap assets, the protocol was designed with stablecoin providers specifically in mind. Stablecoin providers today generally want to maintain avenues to be able to address fraud, theft, and dispute resolution, demanding that they retain insights into the ledger of activity for their assets as well as controls like freezing capabilities. Prior to CAPE, there were no solutions for these types of asset creators to offer privacy-enabled versions of their tokens to users while being able to meet needs around visibility and dispute resolution. With CAPE’s viewing and freezing policies, this is now possible."

Their Other Projects

Configurable Asset Privacy on Ethereum

"CAPE (Configurable Asset Privacy for Ethereum) is a smart-contract application developed by Espresso Systems which enables digital asset creators to determine who can see what information about the activity in the tokens they mint.

Digital assets on CAPE, from stablecoins to NFTs, can be customized to balance transparency, a noted benefit of Web3 products, with privacy, wherever it is required by users. While CAPE transactions appear anonymous and indistinguishable to normal viewers, hiding even the type of asset being transacted, the creator of an asset can configure a viewing policy, which ensures that select parties can decrypt select information about transactions for that asset.

CAPE can be used to create new assets or to wrap assets that already exist on Ethereum, endowing them with privacy properties. Wrapping an ERC-20 with CAPE requires the specification of a wrapper type, which configures who can see what and who can maintain specific controls regarding the assets in question. Wrapping locks the asset in the ERC-20 contract and creates a corresponding CAPE asset of the specified type, while unwrapping burns the CAPE asset and releases the lock."

Hyperplonk and their other Plonk implementations

  • From their blog (24-10-2022):

"Over the past few years, Plonk has become the proof system of choice for most applications in the blockchain space. The reason is that Plonk provides great tradeoffs with short proofs, efficient verification, a high level of customization, and minimal trust assumptions. Unfortunately, Plonk still has limitations, especially when proving large statements or trying to use highly parallel hardware. These limitations are especially important when proving large and complex statements such as rollups and zkEVMs.

To overcome these bottlenecks, we built Hyperplonk. A new zk-proof system with a fully linear time prover and support for high-degree and lookup custom gates. Our prototype Hyperplonk implementation already beats our highly optimized Plonk implementation (Jellyfish), starting from circuits with about 16000 constraints, and the gap keeps growing as statement size increases or more parallelism is used. Hyperplonk also enables high-degree custom gates and lookup, something that is particularly useful for complicated circuits like the ZK-EVM one. These special gates can be used to enable complex EVM OPCODES and building a memory stack."

Roadmap

  • Can be found [Insert link here].

Usage

Projects that use or built on it

Competition

Pros and Cons

Pros

Cons

Team, Funding and Partners

Team

  • Full team can be found here (25-10-2022).

Funding

  • Mentions the following investors on their website (25-10-2022):

Greylock, Electric Capital, Polychain Capital, Scalar Capital, Sequioia, Paxos, Gemini, Robot Ventures, Blockchain Capital, Coinbase Ventures, SLOW, ZKV, Alameda Research

Partners

(:

Knowledge empowers all and will help us get closer to the decentralized world we all want to live in!

Making these free wiki pages is fun but takes a lot of effort and time.

If you have enjoyed reading, tips are appreciated :) This will help us to keep expanding this archive of information.

ETH tip address: 0x83460bE5F218b1520B69D702cE60A1DE37dD8E31