Gabriel

@gcdepaula

85 Following

30 Followers

Gabriel pfp

New fraud-proof algorithm incoming at @devcon! No more Sybil attacks; let’s build truly 1-of-N systems. https://devcon.org/en/sea/schedule/C7ZFH3/ We’ll publish the paper soon. See you in Bangkok :)

0 reply

2 recasts

6 reactions

Gabriel pfp

What are your favorite programming languages? Why?

0 reply

0 recast

0 reaction

Karmen pfp

Super stoked with the line up and guests for the private drinks and debate event we’re cooking up for /ethcc over at @cartesi! Excited to have @trustlessstate and @donnoh.eth on as moderators for our cross-rollup interoperability & fraud proofs panels (personally can’t wait to hear Justin Drake, John Adler, Ed Felten, @tynes & @gcdepaula debate fraud-proof mechanisms)! P.S @vitalik.eth @sassal.eth we want to invite you too! (For lack of a better avenue to reach you guys 😬)

2 replies

3 recasts

9 reactions

Gabriel pfp

Nice article! Quick correction: Dave is permissionless.

0 reply

0 recast

1 reaction

Gabriel pfp

Reminds me of the best article in the internet: http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html > A monad is just a monoid in the category of endofunctors, what's the problem?

0 reply

0 recast

0 reaction

Felipe Argento pfp

Are fault proofs broken? https://ethresear.ch/t/fraud-proofs-are-broken/19234/4 This piece breaks down the problems with current algorithms, gives us a better framework for reasoning about fps and invites us all to a more open and honest research and development process. Great read! Kudos @gcdepaula !

0 reply

1 recast

3 reactions

Gabriel pfp

https://x.com/GCdePaula_/status/1777341549497487753

0 reply

0 recast

0 reaction

Gabriel pfp

Fraud Proofs Are Broken ...but we can fix them A post on why we need to do a better job at permissionless interactive fraud proof research, and on why we should do it together. https://ethresear.ch/t/fraud-proofs-are-broken/19234

1 reply

1 recast

2 reactions

Gabriel pfp

I see! Like this composability layer between other app-specific rollups. We were playing with similar setups: L2 (app-specific) rollup as composability layer, but everything still settling to L1. It relied on cascades, a way to do instant one-way composability between rollups. It feels the possibilities are endless.

0 reply

0 recast

0 reaction

Gabriel pfp

That’s an interesting take! I feel these benefits of L3 you mentioned (cheap compute) are not a property of a “rollup-on-a-rollup”, but a property of application-specific rollups in general. Like, couldn’t you get this cheap compute on an application-specific L2?

1 reply

0 recast

0 reaction

Gabriel pfp

0 reply

0 recast

0 reaction

Gabriel pfp

1- Yeah! These idiosyncrasies make us lose the Rust ecosystem; can’t really expect our fun crates to work out of the box, or easily depend on some external C library. I feel this Solana behavior is actually about the VM, though. It’s insufficiently like our usual computers. Unlike RISC-V, which can even run Linux.

0 reply

0 recast

0 reaction

Gabriel pfp

What’s your take on ISAs like WASM and RISC-V in rollup virtual machines? Any opinions on application-specific rollups?

1 reply

0 recast

0 reaction