|
|
1 jaar geleden | |
|---|---|---|
| .. | ||
| contracts | 7796fbe025 FIx (#1381) | 1 jaar geleden |
| deploy-scripts | 51d5217a57 Fix workspace references | 1 jaar geleden |
| devnet | 084acdb57e [refactor] Convert hyphen to underscore in the directory tree (#524) | 2 jaren geleden |
| examples | 8752291aa2 fix broken links (#945) | 2 jaren geleden |
| sdk | 49d1a579c3 chore: cleanup repo | 2 jaren geleden |
| tools | 51d5217a57 Fix workspace references | 1 jaar geleden |
| wormhole-stub | e5fd5a9d81 [target_chains] Add deployment information for neutron mainnet (#930) | 2 jaren geleden |
| .gitignore | 079828f8ac Wormhole stub (#789) | 2 jaren geleden |
| Cargo.lock | 020ecdf5da Solve (#1539) | 1 jaar geleden |
| Cargo.toml | e1db4aad65 [rust] Remove serde_wormhole patch (#1249) | 1 jaar geleden |
| README.md | a7d133d063 [cosmwasm] CosmWasm integration with contract manager (#1025) | 2 jaren geleden |
This directory contains the Pyth contract for CosmWasm and utilities to deploy it on CosmWasm chains.
We have two kinds of deployment possible on each chain. Stable and Beta. On mainnets we only deploy the stable version. On testnets we deploy both. The purpose of deploying the stable version on testnets is allowing dApps to test their protocol using real accurate price feeds.
This also means we need to somehow distinguish between stable deployments on testnet and mainnets, otherwise a single governance message can affect both of them and have undesired side effects. We do this on cosmwasm by assigning unique chain ids to the testnet and mainnet.
Deploying the CosmWasm contract has three steps:
The scripts directory contains the instructions and scripts to perform all the steps.
We currently have two permissioned networks: injective and osmosis. Uploading the code on their mainnet is not possible without an authority or a governance proposal.