Thread by @bitsplaining

1/ Had an interesting chat with @DavidAKillen today and I think we concluded that a new web3 dev career track is emerging -- the Layer 2 Developer.

🧵👇

2/ While Optimistic #rollups are similar enough to #Ethereum that special expertise is unnecessary,#ZKRollups and hybrid solutions will change that!

3/ A note on hybrid solutions: have seen modular solutions like @bobanetwork that could switch out the proving mechanism from optimistic to zk proofs, and @DCbuild3r's recent article explains we have a trend of "zk-ification" upon us. Keep an eye on this!

4/ The two main players currently in the #ZKRollups scene are #StarkNet and #zksync. Both plan EVM compatibility and promise the (eventual) ability to deploy #Solidity contracts with their protocols.

5/ Both solutions have a "native" language that is better suited for the mathematical computation necessary to fully benefit from the zk architecture being implemented: Cairo for #StarkNet and Zinc for #zksync.

6/ While deploying Solidity code will be possible, there will inevitably be some tasks that are better suited to Cairo or Zinc, particularly computation heavy things that weren't possible on Ethereum's mainnet due to gas costs.

7/ Both StarkNet and zkSync are working to provide robust Solidity support, but if that code is eventually transpiled to Cairo/Zinc, that requires trusting the code doing the transpilation. Or it requires devs with enough expertise in Cairo/Zinc to audit the result!

8/ Web3 teams will likely naturally evolve a "Layer 1/Solidity" team and a "Layer 2 team". The Layer 2 team will write/audit/optimize the code written specifically for #ZKRollups and hybrid solutions.

9/ This analysis opens some questions: what resources exist for devs who want to take on this new area of expertise? What tools would be helpful? We at @trufflesuite are hard at work to provide support for the entire ecosystem of rollup solutions. What do you want to see?