Been diving into EigenLayer AVS lately, sharing my super general and practical understanding of what is it for:

* You have some task – like a piece of program, request, onchain action etc. It produces an output.
* You need to prove to a skeptical 2nd party that it’s correct and truly came from that task.
* Here comes a network of machines (AVS), that can re‑execute the task, confirm the result, and get paid for it.
* The 2nd party can cryptographically verify that machines really did this job.
* But what if some of these machines were malicious?
* That's staking comes in – machines put their money to join the network, earn rewards, but risk penalties for bad behavior.

EigenLayer essentially creates a marketplace for computational trust. But another practical question that comes up to me: what are the actual things you’d want to verify with this?

Re: what would you want to verify? Non-exhaustive but what I'm excited about

1. ZkProofs (Succinct, Lagrange, EigenDA)

2. Web2 API and HTTPs returns via zkTLS (cc @dawufi and @eulerlagrange )

3. Exotic oracles for trading and prediction markets (Uma & Polymarket)

thot leadership at /opacity --
host of vibe check podcast 
▶️ https://pods.media/vibe-check
❄️ icebreaker.xyz/dawufi

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

/opacity

and

/eulerlagrange

Founder, designer, & product guy at /basepaint and /eigenlayer

"Poverty of verifiability" - @eulerlagrange 

https://youtu.be/C8_Ii_rGl1A?si=J8otX36cppMbgZNv