polynya pfp
polynya
@polynya
I haven't commented about rollups in several months, if not over a year, so I'm just a casual observer now... Native rollups are pretty cool, and what I meant by "enshrined zkEVM bridge" a couple of years ago (except they've got a wider scope than zkEVMs) However, they are not "enshrined rollups", as I wrote about them at least, which are in-protocol, L1 rollups Overarching thought on rollups: there simply has not been anywhere enough demand to saturate 1,000+ chains by 2025 like I had expected in 2021. Including all L1s and L2s, there's maybe like 10, at most. I'm sure demand will grow, but not to the magnitude anyone expected. It would be prudent to factor in this lower terminal demand in infrastructure designs, instead of just "build it they'll come" hopium. https://x.com/apolynya/status/1629651981768990720
2 replies
62 recasts
152 reactions

JR ↑ pfp
JR ↑
@juli
100%. Imo this means you should (have) strategically focus(ed) more on making the top 3, 5, 10 l2s very good, interoperable, and high activity hubs in the near-term and not launch another (native) l2/l3 (tech stack). That would be the organic next step with more demand for blockspace & mature tech - and prob by then you’d have more parallelized blockspace and don’t even need to further continue horizontally scaling - except for independent projects like games that would just tap into shared interoperability for occasional transfers.
1 reply
0 recast
3 reactions

JR ↑ pfp
JR ↑
@juli
+ spinning up another copypasta l2 rollup with the op or similar stack should be dynamic/elastic with scaling demand up/down and doesn’t require new teams launching their own tokens and fragmenting the space..
0 reply
0 recast
0 reaction