From 59cb2ccd6a6587b9c81a1c3cadd38d9832ff3c73 Mon Sep 17 00:00:00 2001 From: wbnns Date: Fri, 6 Dec 2024 23:01:49 -0100 Subject: [PATCH] docs(notices): Add notice WRT deprecation of Geth archive snapshots --- ...issioning-public-geth-archive-snapshots.md | 37 ++++++++++ .../preparing-for-fault-proofs-on-base.md | 68 ------------------- apps/base-docs/sidebars.js | 2 +- .../tutorials/docs/0_run-a-base-node.md | 6 ++ 4 files changed, 44 insertions(+), 69 deletions(-) create mode 100644 apps/base-docs/docs/notices/decomissioning-public-geth-archive-snapshots.md delete mode 100644 apps/base-docs/docs/notices/preparing-for-fault-proofs-on-base.md diff --git a/apps/base-docs/docs/notices/decomissioning-public-geth-archive-snapshots.md b/apps/base-docs/docs/notices/decomissioning-public-geth-archive-snapshots.md new file mode 100644 index 0000000000..c61c60059e --- /dev/null +++ b/apps/base-docs/docs/notices/decomissioning-public-geth-archive-snapshots.md @@ -0,0 +1,37 @@ +--- +title: Decommissioning Public Geth Archive Snapshots +slug: /decomissioning-public-geth-archive-snapshots +description: Public Geth archive snapshots will be decommissioned on December 15th, 2024. +keywords: + [ + Geth, + Archive Node, + Node Snapshots, + Ethereum, + Infrastructure, + Reth, + Snapshots, + Base Node, + Beacon Endpoint, + OP Stack, + ] +hide_table_of_contents: true +--- + +# Decommissioning Public Geth Archive Snapshots + +As part of our ongoing efforts to optimize our services, we will be deprecating the Public Geth Archive Snapshots on _December 15th, 2024_. We understand that this change may affect your operations if you rely on these snapshots for maintaining your Ethereum infrastructure. This notice aims to provide you with a potential path forward and offer solutions to ensure a smooth transition. + +## Recommended Path Forward + +We recommend switching to Reth going forward. We will continue to maintain the Reth archive snapshot. + +If you need continued Geth support, we would advise that you maintain your own snapshot that is specific to your infrastructure e.g. EBS on AWS. + +To sync a Geth Archive node to tip: + +- Download the latest Geth Archive snapshot ~30 days old +- Use a beacon endpoint with historical blob data + - Alternatively you can run your own [blob archiver](https://github.com/base-org/blob-archiver) if you don't want to rely on a third party + +If you have any questions or would like assistance, please reach out to us on [Discord](https://base.org/discord) or [GitHub](https://github.com/base-org/base-node). diff --git a/apps/base-docs/docs/notices/preparing-for-fault-proofs-on-base.md b/apps/base-docs/docs/notices/preparing-for-fault-proofs-on-base.md deleted file mode 100644 index 8f68c6ff57..0000000000 --- a/apps/base-docs/docs/notices/preparing-for-fault-proofs-on-base.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Preparing for fault proofs on Base -slug: /preparing-for-fault-proofs-on-base -description: Fault proofs are expected to go live on Base Mainnet in late October. -keywords: - [ - Fault proofs, - Base, - L2 decentralization, - Permissionless output proposals, - Permissionless challenges, - Withdrawals, - Base Mainnet, - DisputeGameFactory, - L2OutputOracle, - Seven-day finalization, - Dispute game, - Bridge operators, - UI updates, - Contract upgrades, - Node operators, - Superbridge, - Superchain bridges, - L1 to L2 deposits, - L2 to L1 withdrawals, - Mid-July upgrade, - Ethereum, - Bridging logic, - Bridge funds, - Decentralized validation, - Community participation, - ] -hide_table_of_contents: true ---- - -# Preparing for fault proofs on Base Mainnet - -Fault proofs are a critical implementation in an L2’s path towards decentralization. They enable a more decentralized approach to validating L2 state and pave the way towards more community participation. - -They improve decentralization with two important capabilities: - -- **Permissionless output proposals:** In an L2 without fault proofs, only the centralized proposer can create and submit output roots about the state of the L2. Now with fault proofs, anyone can make claims about Base's current state instead of relying on a central party. -- **Permissionless challenges to output proposals:** If someone makes a faulty or fraudulent claim, anyone can challenge it. - -These changes allow anyone to withdraw funds from Base to L1 without having to rely on centralized actors. - -## Preparing for fault proofs - -Fault proofs are expected to go live for Base Mainnet in late October. - -**What’s changing for withdrawals:** - -- Withdrawals will involve proving and finalizing based on the fault proof system. -- In addition, the 'DisputeGameFactory' will replace the 'L2OutputOracle' as the new contract for proposing output root statements. This change is part of the broader shift towards the fault proofing system, which is expected to enhance the security and reliability of the platform. - -**If you are in the process of withdrawing your funds from L2 to L1:** - -- **Withdrawals _before_ the upgrade** must wait the 7-day challenge period before finalization. -- **Withdrawals _during_ or _after_ the fault proofs upgrade** for Base Mainnet will be proven by the Fault Proof system and generally take 7 days to finalize, but could see additional delays if challenged. - -**If your team is operating a bridge on Base Mainnet:** - -- Please provide your users with a notice on your UI to inform them that fault proofs will be enabled for Base Mainnet in late October. -- Assess and update your bridging logic, and make sure the new L1 contracts are being used. - -Fault proof contract upgrades will be completed atomically, meaning all affected L1 contracts will be upgraded in a single transaction. No action will be required from node operators. - -Please note, bridge.base.org now redirects to [Superbridge](https://superbridge.app/base) and other bridges (collectively, "Superchain bridges"). Superchain bridges are available to initiate and complete deposits and withdrawals to and from Base. Please refer to our [docs](https://bridge.base.org/deposit) for more information on bridging. diff --git a/apps/base-docs/sidebars.js b/apps/base-docs/sidebars.js index 4bf6b60c60..11dad814ed 100644 --- a/apps/base-docs/sidebars.js +++ b/apps/base-docs/sidebars.js @@ -7,7 +7,7 @@ module.exports = { label: 'Notices', collapsible: false, collapsed: false, - items: ['notices/preparing-for-fault-proofs-on-base'], + items: ['notices/decomissioning-public-geth-archive-snapshots'], }, { type: 'category', diff --git a/apps/base-docs/tutorials/docs/0_run-a-base-node.md b/apps/base-docs/tutorials/docs/0_run-a-base-node.md index 809df5a642..fb1e46433c 100644 --- a/apps/base-docs/tutorials/docs/0_run-a-base-node.md +++ b/apps/base-docs/tutorials/docs/0_run-a-base-node.md @@ -105,6 +105,12 @@ If you're a prospective or current Base Node operator and would like to restore In the home directory of your Base Node, create a folder named `geth-data` or `reth-data`. If you already have this folder, remove it to clear the existing state and then recreate it. Next, run the following code and wait for the operation to complete. +:::info + +We will be deprecating the Public Geth Archive Snapshots on _December 15th, 2024_ and recommend switching to Reth going forward. We will continue to maintain the Reth archive snapshot. + +::: + | Network | Client | Snapshot Type | Command | | ------- | ------ | ------------- | --------------------------------------------------------------------------------------------------------------------- | | Testnet | Geth | Full | `wget https://sepolia-full-snapshots.base.org/$(curl https://sepolia-full-snapshots.base.org/latest)` |