We have been receiving questions from various developers building on Celo about what the Celo transition to an Ethereum L2 means for them - just wanted to post an additional short clarification here, so we can link to that in different discussions:
TLDR, from a developer’s perspective the upgrade of Celo to an L2 should work as any hard fork - meaning that changes are done in the client, and for DApps deployed on Celo things should work seamlessly as before.
Hope that helps!
We have received a few detailed questions from the Aave community, who are in the process of deploying on Celo, and naturally the above statement holds true for the Aave DApp as well. We’re super excited for your deployment and are looking forward to seeing you go live soon!
PS One additional related detail, not relevant here but for folks interested: the originally introduced envelope function will be deprecated at the time of the L2 upgrade, however, an updated version of that envelope function (which will be available on the L2 as well) is already live (introduced with the recent Gingerbread hard fork). All of these changes are only relevant for gas payments in other tokens than CELO (details here).