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.

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

Add Sepolia / Base Sepolia support for Base cross-chain #742

Merged
merged 9 commits into from
Feb 19, 2024

Conversation

michalinacienciala
Copy link
Contributor

@michalinacienciala michalinacienciala commented Nov 8, 2023

The Goerli testnet currently used by Threshold/Keep for development purposes was planned to become deprecated with the end of year 2023. Although it's already 2024, the testnet is still live, but it will loose validators over the time and may become unusable at some point. The testnet that was created to replace it is called
Holešky, however it will take some time until it gets integrated with by some of the projects we rely on. As a solution, we decided to switch first to another testnet that is currently live - Sepolia. This testnet's EOL is planned for 2026, which gives us plenty of time to move to Holešky before Sepolia gets deprecated.

The Goerli -> Sepolia migration means that also L2 testnet based on Goerli (Base Goerli) needs to be migrated to Sepolia-based chain (Base Sepolia). In this PR we're adjusting the config used to deploy testnet contracts in the @keep-network/tbtc-v2-arbitrum project. After the update, both deploy to baseGoerli and baseSepolia networks will be supported (we may remove baseGoerli support once we're sure the baseSepolia deployment works as expected).

TODO

Ref: threshold-network/solidity-contracts#150

The Goerli testnet currently used by Threshold/Keep for development purposes is
planned to become deprecated with the end of year 2023. The testnet that was
created to replace it is called
[Holešky](https://github.com/eth-clients/holesky), however it will take some
time until it gets integrated with by some of the projects we rely on.
As a solution, we decided to switch first to another testnet that is currently
live - Sepolia. This testnet's EOL is planned for 2026, which gives us plenty of
time to move to Holešky before Sepolia gets deprecated.
Until Görli is not dead we want to support both testnets.

The Goerli -> Sepolia migration means that also L2 testnet basing on Goerli
(Base Goerli) needs to be migrated to Sepolia-based chain (Base Sepolia).
At the moment Base Sepolia is not supported by Wormhole, so deployment of our
contracts on that testnet is yet not possible. But we're already adding changes
that prepare us for the moment when it will be supported.
Once support is confirmed, we'll need to verify if `wormholeChainID` we use in
the config is correct for the testnet.
@michalinacienciala michalinacienciala added the :shipit: deployment Deployments and CI workflows label Nov 8, 2023
@michalinacienciala michalinacienciala self-assigned this Nov 8, 2023
@michalinacienciala
Copy link
Contributor Author

I've asked Wormhole support if they plan to deploy their contracts on Base Sepolia: https://discord.com/channels/856079283104251944/857225885231611935/1171840544364822628, will let here know once I have some more info.

Earlier Basescan did not support Base Sepolia. Now that this testnet is
supported there, we can change configuration to use Basescan instead of
Blockscout (Basescan is what we use for other networks as well).
Wormhole has added support for Arbitrum Sepolia, Base Sepolia and Optimism
Sepolia testnets. We want to modify the config of our deployment scripts so that
deployment on Sepolia-based L2s would be possible. As the Chain IDs for Wormhole
Sepolia-based networks differ from from IDs for Mainnet and Goerli-based
testnets, we need to set the right value of `...WormholeChainID` constants for
the the right network we're deploying to.
@michalinacienciala michalinacienciala marked this pull request as ready for review January 18, 2024 16:58
Comment on lines +14 to 17
// This ID is valid for both Polygonn Goerli-based Testnet (Mumbai) and
// Mainnet. Wormhole does not support the Sepolia-based Amoy Testnet yet.
// TODO: Update the ID once the support is added.
const polygonWormholeChainID = 5
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how the deploy on baseSepolia will behave when the polygonWormholeChainID does point to the value which is good for Mumbai and Polygon Mainnet, but not for Sepolia--based Amoy... Should I skip this script for now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Until new Polygon testnet is supported by Wormhole, we can skip this script during deploy.

Adding Sepolia-related contracts needed for deployment on `baseSepolia` network:
* `external/baseSepolia/BaseTokenBridge.json` - address taken from
  https://docs.wormhole.com/wormhole/blockchain-environments/evm#testnet-contracts-base-sepolia-84532
* `external/baseSepolia/SolanaWormholeGateway.json` - used the same value as in `baseGoreli`
* `external/sepolia/TokenBridge.json` - address taken from
  https://docs.wormhole.com/wormhole/blockchain-environments/evm#testnet-contracts-sepolia-11155111

NOT included in this commit (but needed for the deployment):
* `external/baseSepolia/BaseWormholeTBTC.json` - in order to get the address we
  need to perform attestation of the Ethereum Sepolia TBTC token on Base Sepolia
  (but atm Base Sepolia is not available on the list of target networks on
  https://wormhole-foundation.github.io/example-token-bridge-ui/#/register)
Locally deployed portal was used to register TBTC.
We're adding artifacts for contracts deployed to Base Sepolia network.
@michalinacienciala
Copy link
Contributor Author

@lukasz-zimnoch lukasz-zimnoch merged commit 2604b3d into main Feb 19, 2024
38 checks passed
@lukasz-zimnoch lukasz-zimnoch deleted the sepolia-support-base branch February 19, 2024 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:shipit: deployment Deployments and CI workflows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants