Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update forkid-9-12.md #2498

Merged
merged 1 commit into from
Nov 22, 2024
Merged

Update forkid-9-12.md #2498

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/cdk/how-to/migrate/forkid-9-12.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The high-level steps in the collaborative process are:

Please read carefully to fully understand the new architecture before starting the process: [https://docs.polygon.technology/cdk/getting-started/cdk-erigon/](https://docs.polygon.technology/cdk/getting-started/cdk-erigon/)

The table below lists the CDK Fork ID 9 components and the new CDK FEP Fork ID 12 component.
The table below lists the CDK Fork ID 9 components and the new CDK FEP Fork ID 12 components.

> 💡 **Please note:** Latest CDK FEP Fork ID 12 components are listed in the [Polygon Knowledge Layer](https://docs.polygon.technology/cdk/releases/stack-components/#cdk-fep-components)

Expand All @@ -63,7 +63,7 @@ The Implementation Provider must prepare in advance for the upgrade to ensure a
3. Scale up the number of provers in advance. It is recommended that you at least double the number of provers up and running for the scheduled upgrade maintenance window.
- Ensure all (majority) of the network batches are verified before starting the upgrade process, otherwise there will be additional downtime as we wait for the network to be ready.
4. Setting up your CDK Erigon node.
- Please see the [cdk-erigon readme](https://github.com/0xPolygonHermez/cdk-erigon/blob/v1.0.3/README.md) for information on Prereqs, configuration files and running cdk-erigon.
- Please see the [cdk-erigon readme](https://github.com/0xPolygonHermez/cdk-erigon/blob/v1.0.3/README.md) for information on prereqs, configuration files and running cdk-erigon.
5. Required CDK-Node pre syncing.
- Run CDK-Node aggregator component in sync only mode in advance to populate its database.
- Run CDK-Node l1infotreesync component in advance to populate the sequence sender database.
Expand Down Expand Up @@ -162,12 +162,12 @@ go run ./zk/debug_tools/datastream-host \
> 💡 Please note: For an isolated chain not attached to the Agglayer the chain admin can perform operational step 4 on their chain’s rollupmanagercontract.
Polygon are not involved. Please check the [upgrade procedure for isolated networks](#contract-upgrade-procedure-for-isolated-networks).

**Please Note:** Wait for Polygon to send the L1 transaction (tx) and confirm it.

4. **Polygon:** Upgrade the Smart Contract (multisig):
- Upgrade rollup to fork 12.
- Wait for the Tx to be finalized.

**Please Note:** Wait for Polygon to send the L1 transaction (tx) and confirm it.

### Steps to Deploy CDK FEP Fork 12 Components
1. It is recommended to back up your DAC node by taking a snapshot of the DAC database.
- **Locate Your PostgreSQL Instance**:
Expand Down