-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethinking L2 information on ethereum.org #13062
Comments
This issue is stale because it has been open 30 days with no activity. |
Update: designs have been prepared and this Q3 will implementation happen. Once the improvements are published, this issue will be closed. Afterwards we will do UX research to monitor impact of the results. |
Update: Implementation has started few weeks ago and should be finalized in Q3. |
This issue is stale because it has been open 30 days with no activity. |
Removing stale, we are finishing up implementation and will link that PR to this when ready |
This issue is stale because it has been open 30 days with no activity. |
An upgrade to our website has been prepared and soon shipped, with that i am clsing this ticket |
Is your feature request related to a problem? Please describe.
Blobs are here and layer 2 activity is surging. The focus of ethereum.org has always been Ethereum Mainnet (L1), but these rapid scaling infrastructure improvements make it clear that ethereum.org should grow into a more comprehensive resource for the Ethereum ecosystem.
We are in the early stages of planning this transition and welcome your thoughts.
Join in on the discussion in Discord
Describe the solution you'd like
Any other suggestions? Feel free to comment here or on discord!
Describe alternatives you've considered
NA
Additional context
No response
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: