-
Notifications
You must be signed in to change notification settings - Fork 195
Add feynman upgrade docs #533
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
75 changes: 75 additions & 0 deletions
75
src/content/docs/en/technology/overview/scroll-upgrades/feynman-upgrade.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,75 @@ | ||
| --- | ||
| section: technology | ||
| date: Last Modified | ||
| title: "Feynman Upgrade" | ||
| lang: "en" | ||
| permalink: "technology/overview/scroll-upgrades/feynman-upgrade" | ||
| whatsnext: { "Euclid Upgrade": "/en/technology/overview/scroll-upgrades/euclid-upgrade" } | ||
| --- | ||
|
|
||
| ### Overview | ||
| This upgrade contains changes such as: | ||
| - Improve compatibility with EVM: | ||
| - opcode `blockhash` | ||
| - pre-compiles `ecPairing` | ||
| - Implemented: | ||
| - [EIP-2935](https://eips.ethereum.org/EIPS/eip-2935): Serve historical block hashes from state | ||
| - [EIP-7623](https://eips.ethereum.org/EIPS/eip-7623): Increase calldata cost | ||
| - Gas fee parameter redesign | ||
| - Post Euclid clean-ups | ||
|
|
||
| ### Timeline | ||
|
|
||
| - **Scroll Sepolia** : Aug 19th, 2025 | ||
| - **Scroll Mainnet** : Jul 22nd, 2025 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please double check the timeline |
||
|
|
||
| ### Compatibility | ||
|
|
||
| This release updates the embedded hard fork block timestamp for Scroll mainnet. | ||
| **Nodes that are not upgraded will be unable to follow the network after the hard fork block.** | ||
|
|
||
| To follow the Feynman upgrade, simply run your node with the `--scroll` flag for mainnet (and `--scroll-sepolia` for testnet). | ||
|
|
||
| If you do not use the `--scroll` flag, then you must update and reimport `genesis.json`. | ||
|
|
||
| Genesis.json difference : | ||
| ```json | ||
| { | ||
| "config": { | ||
| "chainId": 534352, | ||
| ... | ||
| "euclidTime": 1744815600, | ||
| "euclidV2Time": 1745305200, | ||
| "feynmanTime": 1755576000, | ||
| ... | ||
| "scroll": { | ||
| ... | ||
| "genesisStateRoot": "0x08d535cc60f40af5dd3b31e0998d7567c2d568b224bed2ba26070aeb078d1339", | ||
| "missingHeaderFieldsSHA256": "0xfa2746026ec9590e37e495cb20046e20a38fd0e7099abd2012640dddf6c88b25" | ||
| ... | ||
| ``` | ||
|
|
||
| #### Node Operators | ||
|
|
||
| **Mandatory changes:** | ||
| - `--gpo.congestionthreshold` is deprecated and should be removed. | ||
|
|
||
| **Recommended changes:** | ||
|
|
||
| - Enable the direct-to-sequencer endpoint using `--gossip.sequencerhttp <sequencer-url>`. This reduces latency for transaction submission. | ||
|
|
||
| - Scroll mainnet: `--gossip.sequencerhttp https://mainnet-sequencer-proxy.scroll.io` | ||
| - Scroll Sepolia: `--gossip.sequencerhttp https://sepolia-sequencer-proxy.scroll.io` | ||
|
|
||
| For nodes running with `--rollup.verify` or `--da.sync`: | ||
|
|
||
| - Enable the AWS S3 blob data source using `--da.blob.awss3 <s3-bucket-url>`. | ||
| This can be used alongside other blob data sources (`da.blob.beaconnode`, `da.blob.blobscan`, `da.blob.blocknative`). | ||
|
|
||
| - Scroll mainnet: `--da.blob.awss3 https://scroll-mainnet-blob-data.s3.us-west-2.amazonaws.com` | ||
| - Scroll Sepolia: `--da.blob.awss3 https://scroll-sepolia-blob-data.s3.us-west-2.amazonaws.com` | ||
|
|
||
|
|
||
| See more details in the [testnet release notes](https://github.com/scroll-tech/go-ethereum/releases/tag/scroll-v5.8.72). | ||
|
|
||
| Projects requiring additional guidance should open a [ticket on Discord](https://discord.com/channels/853955156100907018/1280768286124146732). | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EIP-2935 and EIP-7623 should be also under "Improve compatibility with EVM".
Actually you can directly copy the outline in the governance doc.