# cLabs Proposal for Celo to transition to an Ethereum L2

**URL:** <https://forum.celo.org/t/clabs-proposal-for-celo-to-transition-to-an-ethereum-l2/6109>\
**Category:** Protocol\
**Created:** [July 15, 2023, 6:20am UTC](https://forum.celo.org/t/clabs-proposal-for-celo-to-transition-to-an-ethereum-l2/6109 "2023-07-15T06:20:21Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![vbuterin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.celo.org/vbuterin/32/8313_2.png) [@vbuterin](https://forum.celo.org/u/vbuterin)\
**Post date:** [July 17, 2023, 11:16am UTC](https://forum.celo.org/t/clabs-proposal-for-celo-to-transition-to-an-ethereum-l2/6109/27 "2023-07-17T11:16:19Z")

</div>

Amazing, and excited to see this! Would love to see the Celo ecosystem come closer to Ethereum.

Some technical questions/feedback:

1. In the diagram, shouldn’t it be the proposers that sends a block to the validator set? Generally in PBFT-style consensus, the proposer moves first.

2. **Would the data submitted to Ethereum contain the signatures, or a SNARK of the signatures, or just the DA certificate**?

3. **On “never reverting” as an objective**. One of the challenges of that is that Ethereum itself can revert, and even post-SSF in extreme cases: during an inactivity leak the finality mechanism would not run and the chain would run on LMD GHOST.

---

_[View the full topic](https://forum.celo.org/t/clabs-proposal-for-celo-to-transition-to-an-ethereum-l2/6109)._