Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Nastya
@nastya
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?
5 replies
5 recasts
55 reactions
Zach
@zherring
This is accurate. Re: what would you want to verify? Non-exhaustive but what I'm excited abour 1. ZkProofs (Succinct, Lagrange, EigenDA) 2. Web2 API and HTTPs returns via zkTLS (cc @dawufi and @eulerlagrange ) 3. Oracles for trades and prediction markets (Uma & Polymarket)
1 reply
0 recast
6 reactions
Jordan
@ruminations
"what are the actual things you’d want to verify with this?" dangerous question
1 reply
0 recast
2 reactions
Monteluna
@monteluna
Verification of LLM output. Airport checkin. Local in person geotagging. Also that system a while ago that allowed you to do zkttls swaps between crypto and venmo.
1 reply
0 recast
2 reactions
Ayush Garg
@axg
you can access/verify/resolve almost anything; take the quote cast as an example https://farcaster.xyz/axg/0xddddf233
2 replies
0 recast
2 reactions
Samuel ツ
@samuellhuber.eth
seems accurate from my understanding too cc @dabit3
0 reply
0 recast
1 reaction
