# VADCOPs: Leveraging STARKs for Tailored Proof Generation

- Speakers: [Héctor Masip Ardevol](https://streameth.org/speakers/hector-masip-ardevol), [Felicià Barceló](https://streameth.org/speakers/felicia-barcelo)
- Channel: [Devcon 7 SEA](https://streameth.org/devcon_7_sea)
- Date: 2024-11-13
- Duration: 22:28
- Watch: https://streameth.org/watch/67344f579dbb7a90e1b0dad9

## Description

VADCOP is a proving method using STARKs to achieve cost-efficiency by focusing on active parts of the execution trace rather than the entire trace. Traditional modular designs, which divide machines into components and use relational arguments, face inefficiencies due to the padding of unused cells with dummy values. VADCOPs optimize performance by allowing maximum modularity and avoiding unused components, making proof generation precise and efficient without unnecessary redundancy.

## About the speakers

### Héctor Masip Ardevol

I am currently working as a research engineer at Polygon. In this role, I contribute to the development of a robust arithmetization, in terms of the extended Algebraic Intermediate Representation (eAIR), for various projects such as the Polygon zkEVM. Furthermore, I ensure the completeness and soundness of the underlying proving system that we use, apart from doing research on the topic of cryptographic proving systems.

### Felicià Barceló

I'm a Senior Computer Engineer working on zkEVM at Polygon, focusing on DSL compilers and arithmetization through state machines. I use these DSL to define the state machines, ensuring they are robust while optimizing their performance. I graduated from UPC (Universitat Politècnica de Catalunya). 

On a personal level, I have a deep passion for mathematics, problem-solving, building innovative solutions, and DIY.


## Transcript

essentially distributing a verifiable binary version of the chain from one machine to another, essentially. And what this diagram is showing is you've got a set of pages and they're all hash verified. Now, what are the implications of all that process? Well, basically what you end up with is very quick sync performance effectively so the big difference between Eragon to an error Eragon 3 is the amount of time it takes to sync something and this is You see this particularly on large chains so Basically my role in the Eragon team. I mainly work on Polygon rather than Ethereum. So, basically, my role in the Aragon team, I mainly work on Polygon rather than Ethereum. So, basically, my role in the Aragon team, I mainly work on Polygon rather than Ethereum. So basically my role in the Aragon team, I mainly work on Polygon rather than Ethereum. So basically my role in the Aragon team, I mainly work on Polygon rather than Ethereum. So basically my role in the Aragon team, I mainly work on Polygon rather than Ethereum. So basically my role in the Aragon team, I mainly work on Polygon rather than Ethereum,
