Hey devs đź‘‹
We’re researchers from the NYU Blockchain Lab (https://blockchain.stern.nyu.edu/), and we’re exploring one of the most important questions shaping the future of Ethereum and blockchain development:
đź’ Can blockchain platforms overcome the scalability trilemma and achieve mainstream adoption?
Layer 2 solutions — like Arbitrum, Optimism, Base, zkSync, StarkNet, Polygon, and Loopring — are key to that future. They enable scalability, lower fees, and improved UX across the Ethereum ecosystem.
We’re reaching out specifically to the Dev.to blockchain developer community because your firsthand experience building, deploying, and experimenting on L2s provides critical insight into how developers evaluate trade-offs between cost, security, tooling, and ecosystem maturity. Understanding these decision patterns helps connect technical scalability efforts with real-world developer behavior and adoption.
We’re conducting a short survey (~12 minutes) to learn more about how users and developers choose which Layer 2 ecosystems to engage with — and what truly drives those choices.
⸻
Survey Details:
• ⏱️ Takes about 12 minutes
• 💻 Best completed on desktop or laptop
• 💎 Participants receive an exclusive NYU Blockchain Lab NFT (POAP) as a thank-you
• 👉 https://nyublockchainlabsurvey.sawtoothsoftware.com/
⸻
Your feedback will contribute directly to open academic research at NYU and help inform improvements in the design, accessibility, and developer experience of Ethereum’s scaling solutions.
We’ll publish summarized, anonymized findings once the study concludes — so the insights can benefit the broader Web3 community.
Thanks for helping advance research at the intersection of blockchain scalability and real-world developer adoption 🙏
— Prof. Daniel Obermeier, NYU Blockchain Lab
Top comments (1)
It’s great to see academic research digging into how developers actually choose between L2s; that insight is often missing in scalability discussions.
We’ve been exploring how scaling could evolve beyond traditional L2 trade-offs, where consensus itself handles computation, not just validation. It’s interesting to think about how that kind of approach might fit into the broader scalability picture you’re studying. Excited to see the findings from your research.