Media attention regarding Tezos Mumbai upgrade

I got inspired by the last thread about Lima upgrade coverage:

Now in around 6h Mumbai will move into the final phase and with this signigicant upgrade its great material for wide media coverage.

Now there are a few articles on Nomadic Labs blog about Mumbai and Rollups:

Also the TezTalk:

From last year the Twitter Spaces with Yann Regis Gianas

But it would be good to cover the space on other media outlets too.
Especially in combination with a SCORU/WASM demo! This has the potential to get great attention :slight_smile:


To be honest I am still not sure how the rollups work. Maybe because I am used to the concept of a “single” Layer 2 like Arbitrum or Optimism. But the Tezos solution is like every rollup is its own Layer 2?

  • I keep hearing that TPS are not a problem but the latency - its possible to increase TPS but not latency. Why?

  • All transactions are still submitted to L1 before reaching the sequencer for L2. If this is the case then I still need to wait 15s for my operation to be submitted?

  • Is it possible to get another blogpost about SCORUs that describes various examples/scenarios?

  • I read often that SCORU is superior compared to other Layer 2 solutions (e.g. Arbitrum, Optimism, Polygon). But I would like to know the facts, why is that the case?

  • We keep reading about 1M TPS on Layer2 but wouldnt that be super expensive? Alone for every rollup to lock 10k Tezos sounds not realistic?

  • When I remember correctly in the Teztalk I heard if we need to scale we just deploy more rollups but this feels so arbitrary - what are the max. numbers possible for a rollup? Often when I try to pitch tezos rollups people are sceptical of the 1m TPS I say. In fact this is not possible to reach with one rollup but with many - so what is the difference: I also could just deploy Arbitrum a hundred times and say it can reach 1m TPS (I did not made that up, this was a response to me in a conversation, and I legit could not answer that)

  • ZK-Rollups are enabled on Mondaynet but there is no single word in the docs that says how to try them out, despite the fact that the blogposts say we are invited to try them out.

  • I read that it is necessary to have a synthetic tezos token on L2. Why is it not possible to use simple Tezos XTZ?

  • It is said that I cannot withdraw from L2 immediately. I must wait two weeks. I see this as a hurdle for onboarding. Noone likes to wait a couple of minutes and especially two weeks to receive their assets. Is this the final design solution?

  • I saw the Marigold tutorial to write your own Kernel. I imagine to easy attract devs etc that there should be a ready “general purpose kernel” available to use/modify/deploy for everyone provided by the core teams? I dont know for example in Rust, Javascript and Ocaml? This would ease the process and attract more people. Is something like this planned or is my idea just plain stupid?

  • Same goes for the EVM/IBC kernel. I think there should also a “general purpose EVM/IBC kernel” available to everyone to modify/deploy…

  • Often I read on Twitter but who will use a rollup - I thought that there will be a “general” rollup for everyone deployed by the core teams, foundation etc and if devs need their own solution they can make use of the available tools and deploy their own too?

  • And how does the validation process work, to validate the rollup, can everyone just join and be a validator? The only requirement is that I do I need to put in a stake as a validator to ensure I will behave honestly?

  • And why do we need for L2 a DAC and DAL?

It makes the impression for me that on one hand everyone shares everywhere some phrases “rollups on tezos!”, “enshrined”, “fraud proof”, “1m TPS”, but the majority cant explain whats behind. Me neither. And when looking for the information it makes the impression that the whole process is rushed.

So many questions and I feel like I have way more… when AMA :face_with_monocle: