@keep-network/tbtc-v2-optimism
Advanced tools
:toc: macro
= Threshold cross-chain - Optimism
This package brings Bitcoin to Ethereum L2 Optimism. For more details please see link:https://github.com/keep-network/tbtc-v2/blob/main/docs/rfc/rfc-8.adoc[RFC 8: Cross-chain Tokenized Threshold BTC]
== How it works?
+----------------------------+ +---------------------------------------------------------------------------+
| Ethereum | | Optimism |
| | | |
| +----------------------+ | | +----------------------+ +-------------------------+ +--------------+ |
| | Wormhole TokenBridge |--|---------|--| Wormhole TokenBridge |--| OptimismWormholeGateway |--| OptimismTBTC | |
| +----------------------+ | | +----------------------+ +-------------------------+ +--------------+ |
| | | |
+----------------------------+ +---------------------------------------------------------------------------+
OptimismTBTC canonical tBTC token on Optimism with a minting authority
delegated to OptimismWormholeGateway.OptimismWormholeGateway is a smart contract wrapping and unwrapping
Wormhole-specific tBTC representation into the canonical OptimismTBTC token.=== Updating Wormhole Gateway mapping
The deployment scripts are responsible for managing updates of the tBTC gateway
addresses across various chains. These addresses are stored in the external/
directory for a specific network, such as optimismGoerli/ArbitrumWormholeGateway.json.
It is important to note that these addresses should remain constant for the
mainnet network. However, there may be instances where a new version of a
cross-chain module is deployed to the testing network, which would require a
manual update of the corresponding address.
=== Deploy contracts
To deploy all contracts on the given network, please run:
yarn deploy --network <network>
Supported networks:
hardhat - for local developmentoptimismGoerli - L2 testing networkoptimism - L2 mainnetCurrently, this module does not deploy any contracts on L1. All the existing
Wormhole contract addresses that are used in this module are stored under
external/<network> dir.
If contracts haven't been built yet or changes occurred, deploy task will build
the contracts before running the deployment script. This command produces
an export.json file containing contract deployment info. Note that for the
chains other than hardhat the following environment variables are needed:
L2_CHAIN_API_URL - URL to access blockchain services, e.g. https://opt-goerli.g.alchemy.com/v2/<alchemy_api_key>L2_ACCOUNTS_PRIVATE_KEYS - Private keys for the deployer and council <0xOwnerPrivKey,0xCouncilPrivKey>OPTIMISM_ETHERSCAN_API_KEY - Optimism Etherscan API keyFAQs
tBTC v2 on Optimism
We found that @keep-network/tbtc-v2-optimism demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Socket Threat Research maps a rare inside look at OtterCookie’s npm-Vercel-GitHub chain, adding 197 malicious packages and evidence of North Korean operators.
Research
Socket researchers identified a malicious Chrome extension that manipulates Raydium swaps to inject an undisclosed SOL transfer, quietly routing fees to an attacker wallet.
Research
/Security News
Another wave of Shai-Hulud campaign has hit npm with more than 500 packages and 700+ versions affected.