Ethereum

Binance Smart Chain

Solana

Celo

LIVE

ENDED

ASSIGNED

About Alchemy Pay

Founded in Singapore in 2017, Alchemy Pay is a payment gateway that seamlessly connects crypto with traditional fiat currencies for businesses, developers, and end users. With its On & Off Ramp solution, NFT Checkout, Crypto Card and Crypto Payments, Alchemy Pay supports payments in 173 countries.
The Ramp is a one-stop solution to buy and sell crypto and fiat, easily integrated by platforms and dApps according to requirements. The NFT Checkout enables direct purchases of NFTs using fiat payment methods. The Crypto Card solution empowers businesses and token issuers to provide users with branded virtual and physical cards for instant global spending. ACH is the Alchemy Pay network token on Ethereum and BNB Smart Chain.

Website: https://alchemypay.org

Twitter: https://twitter.com/alchemypay

Telegram: https://t.me/alchemy_official

Discord: https://discord.gg/alchemypay

LinkedIn: https://www.linkedin.com/company/alchemypay

Medium: https://alchemypay.medium.com/

YouTube: https://youtube.com/@AlchemyPay

𝐀𝐥𝐜𝐡𝐞𝐦𝐲 𝐏𝐚𝐲

We’re excited to invite you to our Community AMA session! This is your opportunity to dive deep, voice your thoughts, ask pressing questions, and engage with our vibrant community.

🕹How to Participate:

-Join our AMA session-Leave your valuable comments and questions under the tweet

🤑Rewards:

🟩Top Contributors: We’ll handpick 10 standout comments and reward the contributors with a share of $200 $ACH.

Leave comments now: https://twitter.com/AlchemyPay/status/1704431598618480715

🟥Lucky Dip: We will randomly select 5 participants to share 300 $ACH each to those who finish the tasks.

🔹Tasks:

1️⃣Follow @AlchemyPay & @AlchemyPayNews_ on Twitter

2️⃣Join Discord: https://discord.gg/alchemypay

3️⃣Join Telegram: https://t.me/alchemy_official

4️⃣RT & Likes: https://twitter.com/AlchemyPay/status/1704140889361105148

📢Please drop your entries with:

Twitter handle:

Telegram handle:

Discord handle:

Comment link:

🚨Note: The amount of participants must be over 30!
🗓Set your calendar: Till 13:00 UTC, Sept.28

Come, be a part of this dynamic discussion, and stand a chance to win exciting rewards. We value your input and look forward to your participation!

🏆Join Our Community AMA: Share Your Insights and Win Exclusive Lucky Rewards!🏆

Ethereum Foundation

### Describe the bug

There are two instances where the word 'the' is duplicated

Staking withdrawals page:
- ''To try out your setup on a testnet first, visit **the the** Goerli Testnet Staking Launchpad to get started.''

Smart contract security page:
- ''Integer underflows happen for similar reasons: **the the** results of an arithmetic operation falls below the acceptable range.''

### To reproduce

Staking withdrawals page
1. Go to https://ethereum.org/en/staking/withdrawals/#faq
2. Expand the 'I operate a validator. Where can I find more information on enabling withdrawals?' question
3. Read the 2nd paragraph
4. See error

Smart contract security page
1. Go to https://ethereum.org/en/developers/docs/smart-contracts/security/#integer-underflows-and-overflows
2. Read the 2nd paragraph
3. See error

### Expected behavior

Remove duplicate 'the' from the text

The final content should be:

Staking withdrawals page
- ''To try out your setup on a testnet first, visit the Goerli Testnet Staking Launchpad to get started.''

Smart contract security page
- ''Integer underflows happen for similar reasons: the results of an arithmetic operation falls below the acceptable range.''

### Screenshots

<img width="909" alt="Screenshot 2024-01-05 at 15 40 08" src="https://github.com/ethereum/ethereum-org-website/assets/37338979/c882c583-2ec6-4531-81a9-fdabf6a6368a">
<img width="649" alt="Screenshot 2024-01-05 at 15 42 29" src="https://github.com/ethereum/ethereum-org-website/assets/37338979/a77723f8-7396-48b8-89c5-3bc510c61132">


### Desktop (please complete the following information)

All

### Smartphone (please complete the following information)

All

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [ ] No

Fix instances of duplicated words

### Describe the bug

There are two errors on the _Active areas of Ethereum research_ page:
- 'Verkle' is misspelled as 'Verkel'
- There is a missing comma in the Community, education and outreach section

### To reproduce

Verkle typo
1. Go to https://ethereum.org/en/community/research/#recent-research-1
2. Check the 4th item on the list
3. See error

Missing comma
1. Go to https://ethereum.org/en/community/research/#community-education-and-outreach
2. Read the first paragraph
3. See error


### Expected behavior

- 'Verkel' should be changed to 'Verkle'
- A comma should be added (**...memes, teaching resources, events...**) in the following sentence:
_This might include blog posts and articles, books, podcasts, memes, teaching resources events and anything else that builds communities, welcomes new starters and educates people about Ethereum._



### Screenshots

<img width="763" alt="Screenshot 2024-01-05 at 15 27 56" src="https://github.com/ethereum/ethereum-org-website/assets/37338979/7c61faa7-4c20-4a0a-9017-f167c2e876ca">
<img width="346" alt="Screenshot 2024-01-05 at 15 28 17" src="https://github.com/ethereum/ethereum-org-website/assets/37338979/de510327-e495-4b37-9dfb-a52540151ed3">


### Desktop (please complete the following information)

All

### Smartphone (please complete the following information)

All

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [ ] No

Fix errors on 'Active areas of research' page

Now that we have benchmarks for EVMMAX precompiles we can experiment with different Montgomery multiplication algorithms. Currently we use [CIOS](https://github.com/ethereum/evmone/blob/v0.11.0/lib/evmmax/evmmax.cpp#L55-L83).

The [reference paper](https://www.microsoft.com/en-us/research/wp-content/uploads/1998/06/97Acar.pdf) we used have a summary of the complexity of each algorithm. However, these may not be directly applicable to small numbers like 256-bit. Check also what other projects are doing.

Optimize EVMMAX montgomery multiplication

The UI is showing the user a message that is not understandable when they upload files larger than what's allowed:

<img width="1842" alt="image" src="https://github.com/ethereum/sourcify/assets/13069972/58c6cf9a-823a-4101-b521-ff762772e60b">


Fix UI message when `413 Payload Too Large`

Simple renaming. If we have the correct fork names throughout, it makes sense to me that Merge -> Paris.

chore: Update the "Merge" fork name to "Paris" within the repo

Optimism

**Is your feature request related to a problem? Please describe.**
Currently, the alternative implementations of OP Stack components, apart from `op-erigon` and `asterisc`, cannot take advantage of the superchain registry. This creates a sharded collection of chain configurations, where components like `op-reth`, `magi`, `hildr`, `op-besu`, `op-nethermind`, `cannon-rs`, the Rust FPP, and whatever comes in the future that isn't written in Golang, cannot take advantage of this package.

**Describe the solution you'd like**
Modularize the superchain registry such that it can be used by all OP Stack components, preparing for a future where our critical infrastructure is implemented in many more languages than just `Go`.

Ideally, this means defining a core implementation, preferably in a language such as `C`, `C++`, or `Rust` that is more friendly for interop, and then creating FFI bindings that enable several front-end APIs to be built for the library.

We currently need support for:
* `Java`
* `Rust`
* `C#`

**Describe alternatives you've considered**
1. Implement separate versions of the `superchain-registry` repository for each language that the OP Stack's core components are built upon. This would require a decent bit of duplicated code, increasing the possibility of divergent configuration between the implementations.
2. Create FFI bindings from the Go implementation. Go does not lend itself well towards being called via FFI, and `Cgo` is a bit horrendous to work with when the direction is `<language>` -> `Go` rather than `Go` -> `<language>`. It requires `cbindgen` to embed Go types and semantics into the C header, etc. Rather than doing this, we should choose a more FFI friendly language that is closer to `C` (or, even `C`/`C++` itself) for the base implementation.

**Additional context**
Modularizing the superchain registry will pay dividends in the future, offering a central, interoperable library for every OP Stack component to share the same configuration utilities.


feat: Support all OP Stack components

Offchain Labs

**Is your feature request related to a problem? Please describe.**
Currently we only support uploading das data to aws s3 or locally, we would like to support more cloud providers for storage so that we can decentralize the risk of centralized failures and reduce maintenance costs.

**Describe the solution you'd like**
Add google cloud storage(GcsStorageService) 


Feature: Adding google cloud storage support to DAS

2 steps to update this page https://docs.optimism.io/builders/tools/monitoring/analytics-tools:
1. Update the list of OP Dashboards
    - [[OP Stack Chains - L1 Mainnet Activity & Fees Paid, L2 OP Chain Activity](https://dune.com/oplabspbc/op-stack-chains-l1-activity)](https://dune.com/oplabspbc/op-stack-chains-l1-activity)
    - [[OP Mainnet Protocol Metrics](https://dune.com/optimismfnd/Optimism)](https://dune.com/optimismfnd/Optimism)
    - [[Popular Apps on OP Mainnet and Project Usage Trends](https://dune.com/optimismfnd/Optimism-Project-Usage-Trends)](https://dune.com/optimismfnd/Optimism-Project-Usage-Trends)
    - [[OP Token House Delegates](https://dune.com/optimismfnd/optimism-op-token-house)](https://dune.com/optimismfnd/optimism-op-token-house)
    - [[Superchain NFTs](https://dune.com/oplabspbc/superchain-nfts)](https://dune.com/oplabspbc/superchain-nfts)
2. Add additional tools/resources (i.e. our github, defillama, growthepie)
    - DeFi Stats: https://defillama.com/
    - L2 Usage and comparison: https://www.growthepie.xyz/
    - OP Analytics (incentive tracking, helper functions, public analysis): https://github.com/ethereum-optimism/op-analytics
    - Contribute to NumbaNERDs: https://app.dework.xyz/optimism-community/main-space-35638/overview or requests: https://github.com/ethereum-optimism/op-analytics/issues

[AUDIT] update analytics-tools

[AUDIT] new tutorial: op-viem

for this page: https://docs.optimism.io/builders/dapp-developers/bridging/custom-bridge

we can link to some custom bridges to help explain this more (eg the NFT bridge) 

[AUDIT] Add custom bridge examples

As outlined below, it might be nice to just have one page outlining all JS tools and how they fit into each other. This draft is how I imagine them relating to each other.

- The sdk, [[op-viem](https://www.opviem.sh/)](https://www.opviem.sh/), [[fee-estimation](https://github.com/ethereum-optimism/optimism/tree/develop/packages/fee-estimation)](https://github.com/ethereum-optimism/optimism/tree/develop/packages/fee-estimation) are all a class of “JS libraries that bridge the gap between Ethereum and the OP Stack.” 

Here’s what’s potentially the right abstraction:

- In JS tools, explain that OP Mainnet and OP Stack chains are automatically compatible with many Ethereum JS tools, and we provide subsidiary libraries for the different functions: bridging & gas
    - Ethers v5
        - the SDK provides the different functions
    - Ethers v6
        - (the plugin is incoming, a draft of it at https://github.com/ethers-io/ext-utils-optimism
    - Viem
        - op-viem handles bridging; fee-estimation handles fees, but both will be merged into op-viem
    - web3.js
        - fees handled by the [[web3.js-plugin](https://github.com/ethereum-optimism/optimism/tree/develop/packages/web3js-plugin)](https://github.com/ethereum-optimism/optimism/tree/develop/packages/web3js-plugin)

[AUDIT] Add JS tools overview page

revisions for this page: https://docs.optimism.io/builders/chain-operators/tutorials/sdk
- This tool is relevant for OP Mainnet developers too, there should probably be a reference to it there, maybe just as a link to this page
- There are lots of smaller tutorials around the SDK all over the docs, might be nice to put them all in one place by linking them here!

[AUDIT] Add more links to diff sdk tutorials

suggested changes for https://docs.optimism.io/builders/cex-wallet-developers/wallet-support
- update for gotchas when running a smart contract wallet 
- link to some guide on how to use the RPC
- link to [this page](https://docs.optimism.io/stack/transaction-fees/overview) for the fee section since wallet providers ask about this often

[AUDIT] Wallet support page revisions

## Brief Description of the Docs Request
There are a few outstanding items on [rpc methods](https://docs.optimism.io/node-operators/json-rpc) that require updating from a developer running an op stack chain. 

## Description of the Documentation You'd Like

- [ ] [admin section](https://docs.optimism.io/node-operators/json-rpc#admin), needs description
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_resetderivationpipeline), needs sample success output
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_startsequencer), missing sample success output
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_stopsequencer), needs sample success output
- [ ] [this last item](https://docs.optimism.io/node-operators/json-rpc#admin_sequenceractive), missing sample success output

## Links to Related Pages
n/a

## Additional Context
We want to provide the community with complete documentation. :)

[DOCS] Update RPC methods with op stack chain info

https://github.com/ethereum/solidity/releases/tag/v0.8.23

Update framework tests and docs for solc 0.8.23

## Brief Description of the Docs Request
Feedback from devconnect about dev-node tutorial

## Description of the Documentation You'd Like
I'll point out some minor issues in the docs that we noticed during setup:

- The [optimism docs](https://community.optimism.io/docs/developers/build/dev-node/#) do not mention that you need to build the bedrock contracts prior to the deployment (only the [github wiki](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/specs/meta/devnet.md) has this info).
- The contracts are located in the packages/bedrock-contracts, while the github wiki instructs to build from packages/contracts (does not exist).
- When building the contracts using yarn (as per the guidelines in the docs), we were prompted to use pnpm instead. Using pnpm the installation and build process worked fine.

## Links to Related Pages
n/a

## Additional Context
dev-node tutorial and github wiki need to be updated to match

[FEEDBACK] Update dev-node tutorial + github wiki

when running a private L1 network,  the CREATE2 factory contract is not already deployed.

The steps that they would need to take:
• spin up private L1 network
• fund the create2 deployer account and deploy the create2 deployer
    ◦ These two commands can be found on the <https://github.com/ethereum-optimism/optimism/blob/536b44b0c6b5317c6a5dba9bad85ebdd069cbac8/bedrock-devnet/devnet/__init__.py#L123-L133|devnet init script>
• deploy the  L1 contracts (they will use the create2 deployer)
• deploy the OP Stack


[TUTORIAL] run op stack on a private L1 network

## Description

In https://github.com/ethereum-optimism/mocktimism/pull/46 we added a way of publishing mocktimism to npm. To make it cross platform we need to add postinstall scripts.  Example of this is here https://github.com/ethereum-optimism/mocktimism/pull/46

## Tasks

- [ ] Add necessary scripts

Make npm package cross platform

## Description

We don't want to write docs for the cli we want to generate it in a script. It appears pretty easy to do looking at this https://github.com/urfave/cli/pull/830. We also want to make s

## Tasks

- [ ] Add a new `scripts/` package
- [ ] Add a script to generate markdown doc for cli app into docs/cli.md
- [ ] (optional) Add check to circleci config that make sure generated docs are up to date

[Nice to have] Generate markdown docs about the cli from urfavecli

Opening up discussion for requirements / ideas for creating an open-source registry for any and all OP Chains & OP Stack Forks.

**Problem:**
Crypto data teams have a super hard time keeping track of deployed OP Chains & OP Stack Forks. Some chain deployers attempt to get in touch with OP Labs / OP Foundation, but otherwise this requires sleuthing through Twitter, blog posts, news aggregators, etc. Many people maintain their own lists with varying degrees of comprehensiveness (nobody knows how many production mainnet chains actually exist)

To solve for this, want to create a shared open-source resource for analysts, developers, educators, etc to identify OP Chains & OP Stack Forks with the relevant information about them.

See [Key Definitions for Chain Segments](https://community.optimism.io/docs/contribute/important-terms/#the-superchain)

**Goals:**
- Be the best "source of truth" for identifying metadata for OP Chains & OP Stack Forks
- Store relevant information for analysts (i.e. Name, RPC, Block Explorer, L1 Contracts, Chain Configuration)
- Make it SUPER easy to contribute to (i.e. easy to add new chains, easy to modify data, easy to add bespoke attributes)
- Make it SUPER easy to read from (i.e. if we input in yml, outputs are available in csv, json, sql, etc)
- Provide the necessary metadata for analysts to create chain segments (i.e. RAAS provider, DA Layer, other Config Changes, potential superchain compatibility)
- Be scalable, we don't want to have to re-do this if/when there are thousands of chains

**Existing Version(s):**
- op-analytics Repo [`chain_metadata`](https://github.com/ethereum-optimism/op-analytics/blob/main/op_chains_tracking/inputs/chain_metadata.csv)
- Dune Upload from OP Labs CRM [`dataset_op_stack_chain_metadata`](https://dune.com/queries/3109219)
- [superchain-registry](https://github.com/ethereum-optimism/superchain-registry) repo
- [superchain.eco](https://www.superchain.eco/ecosystem/chains)

**Other Inspiration / Attempts:**
- [L2Beat](https://l2beat.com/scaling/summary)
- [growthepie](https://www.growthepie.xyz/)
- [Kofi's Rollup Economics](https://dune.com/niftytable/rollup-economics)
- [OP Stack Data Dashboard](https://dune.com/oplabspbc/op-stack-chains-l1-activity)
- [ethereum-lists/chains](https://github.com/ethereum-lists/chains)

**Open Questions:**
- What are the top use cases for this? (_Non-Labs teams, please share!_)
- What fields do we need to track? What "requirements" should this have?
--
- What's the best input format (i.e. csv, yml), output formats to be available (i.e. csv, json, sql cte)?
- What is the right organizational structure? (i.e. one ecosystem/chain deployer can have multiple chains, there may be a gazillion chains)
--
- How can we "automate" parts of this? (i.e. identify new L2s via L1 contracts - somehow tie that back to metadata)
- What could/should be onchain?
--
- What's the process for accepting/rejecting/verifying changes?
- How do we incentivize chain deployers to "register"?

[Idea Discussion] Open-Source OP Chain & OP Stack Forks Metadata Source

In this section https://stack.optimism.io/docs/build/getting-started/#deploy-the-l1-contracts, after you broadcast the L1 contracts the folder that gets updated is deployments/goerli and the folder you make deployments/getting-started remains empty. The follow command to generate the genesis and rollup files assumed deployments/getting-started is populated but it's empty and errors. I have been copying the goerli folder to getting-started to be consistent with the command
Step 4 in https://stack.optimism.io/docs/build/getting-started/#configure-your-network asks you to put your PRIVATE_KEY in the .envrc but doesn't specify using the raw privkey and not the hex prepended 0x... key
I don't think there's a section on which address/steps on how to bridge back out (understand this takes a while to actually execute, but unless I missed it I don't think the info is there)
Small note when you're configuring your files to change the batcher inbox address to something arbitrary would be helpful to users
Proposed ETH amounts for Admin — 2 ETH Proposer — 5 ETH Batcher — 10 ETH is probably a bit high, Goerli is super cheap 🙂
Pin the optimism and geth tags/versions here https://stack.optimism.io/docs/build/getting-started/#build-the-optimism-monorepo - trying this guide from a latest tag has many config values missing or missing steps, I am using v1.1.4 and it seems fine
The RPC port by default is 8545, a note on which piece of the software has the flag to change this and a note about ssl setup with it would help

[FEEDBACK] Update op-stack getting started

### Describe the bug

H4's on /staking pages appear to have grown in size to 36px from 20px.

### To reproduce

1. Go to https://ethereum.org/en/staking/#comparison-of-options
2. See size of H4's


### Expected behavior

This is what is was previously like (and would expect):

<img width="1731" alt="image" src="https://github.com/ethereum/ethereum-org-website/assets/54227730/e5a34abf-5048-4362-830e-4aafde240cde">


### Screenshots

Currently:

![image](https://github.com/ethereum/ethereum-org-website/assets/54227730/3f5794a6-327f-4602-bbf2-8268a2c46c62)


### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

@nloureiro or @konopkja if you could confirm this

### Would you like to work on this issue?

- [ ] Yes
- [X] No

H4 sizing on /staking page

*To make our work more accessible and to foster more community collaboration, our team publishes an overview of our quarterly roadmap goals. See last quarter's roadmap here: #10666.*

**Greetings fellow Ethereans!**

[Our vision with ethereum.org](https://ethereum.org/en/about/) continues to be to create the best portal for Ethereum's growing community. We’re an educational resource focused on helping onboard millions of visitors to Ethereum each month. Here's a look at our major Q4 initiatives to advance this vision.

Quick point of clarification: ***this is the roadmap for [ethereum.org](http://ethereum.org/) the website, not Ethereum the protocol***. If you’re looking for the Ethereum roadmap, check out information on [upcoming network upgrades](https://ethereum.org/en/roadmap/) and learn more about [Ethereum governance](https://ethereum.org/en/governance/).

With that out of the way, let’s dive in.

## 🖊️ Writing cohort v2

The engagement with our May 2023 edition of the [ethereum.org](http://ethereum.org) writers' cohort was so impressive that we're excited to announce we'll be running a second cohort! Registration is already open, and the cohort starts on October 20th.

The writers' cohort is a 3-week online writing program for anyone interested in writing about Ethereum. During the cohort, participants will attend weekly workshops, publish articles on topics of their choice, and receive support and feedback from our global community.

[_Join the ethereum.org's writers cohort_](https://ethereumwriterscohort.carrd.co/)

## 🦄 Plan 2024 community acknowledgements

For the contributors 👀!

In Q4, we'll plan our contributor acknowledgement campaign for all of 2024, including different types of acknowledgements, different platforms we plan to use, tiered acknowledgements for different types of contributors, and a unified contributor campaign to further reward contributing to ethereum.org

## 🇹🇷 Devconnect prep

[Devconnect](https://devconnect.org/) is set to be the biggest Ethereum event in 2023, and the entire [ethereum.org](http://ethereum.org) team will be attending! This initiative will cover everything from ensuring we all arrive safely in Istanbul to creating swag for and organizing an ethereum.org event for contributors while we're there.

We hope many of our outstanding contributors will attend, and we'd love to see you there! If you plan to be at Devconnect, [give us a ping on Discord](http://ethereum.org/discord)!

## 📜 Redesign menu navigation

Our website's has grown to over 300 pages. The more pages that exist, the harder it is for users to navigate and find information.

We've noticed a few problems: a lack of user guidance, difficulty finding content in the subpages, difficulty finding new content, and visual inconsistency between menu items.

In Q4, we'll redesign the menu navigation to improve the user experience, with the goal of implementing the changes in early Q1.

## 🍁 Design system: content tabs and third-level navigation

Our Design System is an ongoing initiative started in 2022. As we move forward, we'll continue comprehensive breakdowns of our plans each quarter.

In Q4, our focus will be on:

- Redesigning our third-level navigation concurrently with the main navigation overhaul
- Streamlining the design of content tabs across the website

_We welcome your thoughts – we'll share our progress and seek feedback in our design channel on Discord. Want to get involved? [Join us on Discord!](http://ethereum.org/discord)_

## 👛 Find wallets design improvements

The Find Wallet page is a crucial component of our website, with a high traffic volume and an intricate UI/UX design. Due to its high impact, we will further improve its functionality and user experience in Q4 by:

- Rethinking the mobile experience, as this page receives the highest mobile traffic.
- Improving the wallet selection process for new users
- Reviewing filters and personas to reflect ecosystem developments

_[Join our Discord to get involved and see updates on the design changes](http://ethereum.org/discord)_

## 🌱 Seed phrase page

While we have content on wallets, password security, and accounts, we need better content explaining how seedphrases work.

These foundational topics can empower users to understand the importance of these words, why keeping them safe matters, and how to use them.

We'll write more detailed, technical information in the future, but for Q4, we'll focus on beginner-level content, including:

- Demystifying the terminology
- Illustrating how these words can generate multiple keys
- Clarifying that key generation adheres to a standard and alleviating concerns about longevity and transferability
- Highlighting common threats, behaviours to avoid, and strategies to bolster security

Want to learn more? We’ll share our brainstorming and work-in-progress in [our content channels on Discord](http://ethereum.org/discord)

## 📉 GitHub Zero!

During Q4, we will increase the time we, as the core team, spend reviewing GitHub issues and pull requests. The goal will be returning to maintenance mode we have outlined for [issues](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/github-issue-triage-process.md) and [pull requests](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/review-process.md).

Friendly reminder that we encourage input from the community [you're free to review and give input to any open issue or pull request](https://github.com/ethereum/ethereum-org-website/pulls).

## 🍴 Dencun Content Updates

The next major Ethereum upgrade, Dencun, is expected for a Q4 2023/Q1 2024 release. This upgrade will drastically reduce layer-2 fees via the Proto-Danksharding (EIP-4844) implementation.

In Q4, we will:

- Introducing content related to the upgrade
- Advising node operators to update their setups
- Educating users about the changes and their impact

## 🛣️ 2024 roadmapping and budget

2023 was a big year for ethereum.org, and we want to make 2024 an even bigger one. As part of this initiative, we'll devote time to planning out our roadmap and budget for 2024 by reflecting on what we've done, where we are, and where we want to go.

If you're interested in the longer-term vision of ethereum.org, [join our Discord](http://ethereum.org/discord). We'll plan our completed high-level plans with the community by the end of the year!

## 🕊️ Migrate to NextJS

A carry-over project from Q3, our goal is to transition our website from Gatsby to NextJS, completing the move in Q4.

A significant chunk of our Q4 efforts will be channelled towards testing and quality assurance of the migration. We'll be relying on the community to help us test for bugs and issues. [Join our Discord to help](http://ethereum.org/discord)!

## 🪐 Migrate Platform to Netlify

We currently use Gatsby Cloud for our weekly website builds and deployments. Unfortunately, Gatsby Cloud is being discontinued, with its services stopping on October 30th.

In Q4, we'll transition from Gatsby Cloud to Netlify. This will ensure our contributors continue to benefit from preview deploys on their pull requests and that we can continue to release new content weekly without interruption.

## 💯 Quizzes bug

In Q2, we launched our new and popular quiz hub.

Due to some technical details of how it was built, we can't add new quizzes to the hub. In this relatively small epic, we will refactor the quiz hub code to enable us to expand the quiz hub to include the 10+ new quizzes we've already written 🎉

Want to help? [Learn more in the GitHub issue.](https://github.com/ethereum/ethereum-org-website/issues/10887)


# How does that sound?

We always appreciate feedback on our roadmap - if there's something you think we should work on, please let us know! We welcome ideas and PRs from anyone in the community.

Get involved: [Learn more about contributing](https://ethereum.org/en/contributing/), [hit us up on Twitter](https://twitter.com/ethdotorg), or join the community discussions in [our Discord](https://discord.gg/CetY6Y4).

Q4 2023 ethereum.org product roadmap

### Describe the bug

wrong aligment:

 too much white space in cards (https://ethereum.org/en/what-is-ethereum/)
![Screenshot 2023-10-03 at 22 03 25](https://github.com/ethereum/ethereum-org-website/assets/100724231/6c3f5288-b370-43be-909b-baad8c85f59a)

expected design: (see https://ethereum.org/en/get-eth/)
![Screenshot 2023-10-04 at 16 46 53](https://github.com/ethereum/ethereum-org-website/assets/100724231/a15fb2de-bb9d-4cae-8905-e849e331096c)



### To reproduce

1. use mobile device
2.  Go to https://ethereum.org/en/what-is-ethereum/

### Expected behavior

see other comments

### Screenshots

_No response_

### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

Wrong paddings on What is ethereum page (mobile)

### Describe the bug

Dates on event cards are not being formatted using intl locale.

### To reproduce

1. Go to https://ethereum.org/zh/community/events/
2. Notice date format in event cards compared to date at the top of the page.

### Expected behavior

Despite the contents of these cards not being translated into other languages, I would expect these dates to be rendered according to the locale.

The [`Intl.DateTimeFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat) should be used by passing the current locale and the date to render accordingly.

### Screenshots

<img width="866" alt="image" src="https://github.com/ethereum/ethereum-org-website/assets/54227730/7462d64f-361f-415b-9892-8e4b1a784ae7">


### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

Incorrect intl number formatting

Currently there is no built-in support for tracing in the ethclient/gethclient. This involves adding 4 new methods to gethclient:

- TraceCall
- TraceTransaction
- TraceBlock
- TraceChain

Support tracing API in gethclient

Uniswap

`ApproveERC20` is only used to set max approvals on OpenSea's conduit + Sudoswap for NFT trades, and doesn't really fit well into the Payments module in Universal Router.

Separate out approveERC20 from Payments.sol into separate file

**Is your doc request related to a problem or existing docs? Please describe.**

One of our users lost their ERC20s by directly sending them to a bridge implementation contract.

**Describe the documentation you'd like**

Create new user documentation around bridging tokens and ether with multisig (Safe) wallets.

**Additional context**
Add any other context or screenshots about the feature request here.


[DOCS] add instructions on how to bridge ERC20s/ETH with multisig wallets

https://docs.estuary.tech/Reference/SwaggerUI

Contribute to top web3 projects

Learn, earn and showcase by contributing to bounties on open source issues to help ecosystems to grow!