-
Notifications
You must be signed in to change notification settings - Fork 271
Added banner and notice page for SDK deprecation #928
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 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
933f422
Added notice page for deprecation and banner
krofax 1380502
updated docs
krofax 59c12d8
updated content
krofax f67bb4f
updated docs
krofax cdeb332
Added a lang attribute
krofax 924eceb
Used sentence case for headers
krofax 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
{ | ||
"granite-changes": "Preparing for Granite Breaking Changes", | ||
"fp-changes": "Preparing for Fault Proofs Breaking Changes" | ||
"fp-changes": "Preparing for Fault Proofs Breaking Changes", | ||
"sdk-deprecation": "Preparing for Optimism SDK deprecation" | ||
} |
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,100 @@ | ||
--- | ||
title: Deprecation of the Optimism SDK | ||
description: This page outlines the details of the Optimism SDK deprecation and guides developers to migrate to using `viem/opstack` library. | ||
--- | ||
|
||
## Preparing for Optimism SDK deprecation | ||
|
||
The Optimism SDK will officially be deprecated on **\[insert deprecation date]**. We are shifting to the `viem/opstack` library for a more modern, efficient, and flexible development experience. This change affects all tutorials and resources that previously relied on the Optimism SDK, and we have updated relevant documentation accordingly. | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
### Breaking Changes to Expect | ||
|
||
The migration from the Optimism SDK to `viem/opstack` library brings several breaking changes: | ||
|
||
* **Transaction estimation**: Methods for estimating gas fees will now leverage `viem` APIs. | ||
* **Bridging**: All token bridging actions must be updated to use the `viem/opstack` library bridging methods. | ||
* **Cross-chain communication**: `viem/opstack` library simplifies the cross-domain messaging functionality. | ||
* **SDK method removal**: All deprecated SDK methods will be unavailable after \[insert deprecation date]. | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
We strongly encourage developers and users to transition to `viem/opstack` before the deprecation date to avoid disruptions. | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
### Updated Tutorials | ||
|
||
We've updated our tutorials and documentation to use `viem/opstack` library. Below, you'll find links to the updated versions of popular tutorials: | ||
|
||
* [Estimating Transaction Costs on OP Mainnet](../tutorials/transaction-cost-estimation)\ | ||
Estimation of transaction costs now uses the `viem` gas estimation utilities. | ||
|
||
* [Triggering OP Mainnet Transactions from Ethereum](../tutorials/trigger-op-transactions)\ | ||
Learn how to trigger transactions using `viem` to interact with the OP Mainnet. | ||
|
||
* [Tracing Deposits and Withdrawals](../tutorials/tracing-deposits-withdrawals)\ | ||
The tracing functionalities have been adapted to use `opstack` for efficient results. | ||
|
||
* [Viewing Deposits and Withdrawals by Address](../tutorials/view-deposits-withdrawals)\ | ||
This tutorial outlines updated methods in `viem` for querying deposits and withdrawals by address. | ||
|
||
* [Bridging Your Standard ERC-20 Token Using the Standard Bridge](../tutorials/bridge-standard-erc20)\ | ||
The standard bridge tutorial now uses `opstack` for token transfers between Ethereum and OP Mainnet. | ||
|
||
* [Bridging Your Custom ERC-20 Token Using the Standard Bridge](../tutorials/bridge-custom-erc20)\ | ||
Custom ERC-20 tokens can now be bridged via `opstack`, making the process more streamlined. | ||
|
||
* [Bridging ERC-20 Tokens to OP Mainnet With the Optimism SDK](../tutorials/bridge-sdk-erc20)\ | ||
**Deprecated** – please use [Bridging Your Custom ERC-20 Token Using the Standard Bridge](../tutorials/bridge-custom-erc20). | ||
|
||
* [Bridging ETH to OP Mainnet With the Optimism SDK](../tutorials/bridge-sdk-eth)\ | ||
**Deprecated** – please use [Estimating Transaction Costs on OP Mainnet](../tutorials/transaction-cost-estimation). | ||
|
||
* [Communicating Between OP Mainnet and Ethereum in Solidity](../tutorials/cross-chain-solidity)\ | ||
Cross-chain communication now leverages `opstack` for all messaging. | ||
|
||
### For App Developers | ||
|
||
If your application currently depends on the Optimism SDK, you will need to migrate to using the `viem/opstack` library. | ||
Our tutorials have been updated to reflect these changes, and it is critical to update your applications before the deprecation date to maintain compatibility. | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
Here are some key points to consider: | ||
|
||
Install new dependencies: Replace the Optimism SDK with `viem/opstack` in your project. | ||
|
||
```bash | ||
pnpm remove @eth-optimism/sdk | ||
npm install viem | ||
``` | ||
|
||
* Update imports: Replace Optimism SDK imports with `viem/opstack` imports. | ||
* Migrate SDK methods: Refactor your code to use equivalent `viem/opstack` methods. Refer to the viem documentation and opstack documentation for guidance. | ||
* Test thoroughly: After migration, extensively test your application to ensure all functionality works as expected. | ||
|
||
### For Chain Operators | ||
|
||
Chain operators utilizing the SDK for cross-chain operations, bridging, or other functions should switch to the `viem/opstack`. | ||
The `viem/opstack` library offer more efficient methods to handle these operations. | ||
|
||
Chain operators should be aware of the following: | ||
|
||
* SDK removal: Remove any dependencies on the Optimism SDK in your infrastructure. | ||
* Update tooling: Ensure all tools and scripts are updated to use `viem/opstack`. | ||
* Monitor performance: After migration, closely monitor your chain's performance to ensure smooth operation. | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
### For Node Operators | ||
|
||
Node operators will need to ensure that any scripts or services relying on the Optimism SDK are updated to use `viem/opstack` library. | ||
These updates will help align with future improvements and scalability efforts across the OP Stack. | ||
|
||
Node operators should take the following steps: | ||
|
||
* Update node software: Ensure your node software is compatible with the latest `viem/opstack` libraries. | ||
* Review configuration: Check and update any configuration files that may reference the Optimism SDK. | ||
* Test thoroughly: Perform comprehensive testing in a staging environment before updating production nodes. | ||
|
||
### Need Help? | ||
|
||
For further assistance or questions about this migration, feel free to reach out via the | ||
|
||
* [Community forum](https://community.optimism.io/) or | ||
* [Join our developer Slack](#). | ||
* Join our [Discord](#) for community support | ||
* Open an [issue on our GitHub repository](#) | ||
* Check our [FAQ](#) for common questions and answers | ||
krofax marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -230,6 +230,7 @@ offchain | |
Openfort | ||
oplabs | ||
opnode's | ||
opstack | ||
Opti | ||
pausable | ||
pcscdpath | ||
|
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.