GitBross Sākums Izpētīt Palīdzība
Reģistrēties Pierakstīties
sol_BMCMMXZh
/
pyth-network_pyth-crosschain
1
0
Atdalīts 0
Faili Problēmas 1 Izmaiņu pieprasījumi 0 Vikivietne
Atzars: chore(contract-manager)-new-entropy-script
Atzari Tagi
pyth-network_py...
/
target_chains
/
cosmwasm
Ali Behjati b5ae884eba refactor(js): move ts-node to package catalog (#2513) 8 mēneši atpakaļ
..
contracts ee557d20a3 refactor: move wormhole attester to pythnet_sdk legacy module (#2353) 9 mēneši atpakaļ
deploy-scripts b5ae884eba refactor(js): move ts-node to package catalog (#2513) 8 mēneši atpakaļ
devnet 084acdb57e [refactor] Convert hyphen to underscore in the directory tree (#524) 2 gadi atpakaļ
examples 955a805e85 chore: apply rustfmt 1 gadu atpakaļ
sdk 1e692e1de2 Deny clippy warnings in CI properly (#2109) 1 gadu atpakaļ
tools b5ae884eba refactor(js): move ts-node to package catalog (#2513) 8 mēneši atpakaļ
wormhole-stub e5fd5a9d81 [target_chains] Add deployment information for neutron mainnet (#930) 2 gadi atpakaļ
.gitignore 079828f8ac Wormhole stub (#789) 2 gadi atpakaļ
Cargo.lock ee557d20a3 refactor: move wormhole attester to pythnet_sdk legacy module (#2353) 9 mēneši atpakaļ
Cargo.toml e1db4aad65 [rust] Remove serde_wormhole patch (#1249) 1 gadu atpakaļ
README.md a7d133d063 [cosmwasm] CosmWasm integration with contract manager (#1025) 2 gadi atpakaļ

README.md

Pyth CosmWasm

This directory contains the Pyth contract for CosmWasm and utilities to deploy it on CosmWasm chains.

Deployment types

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.

  • Stable deployments are controlled by the upgrade multisig deployed on mainnet and accept price feeds that originate from pythnet.
  • Beta deployments are controlled by the upgrade multisig deployed on devnet and accept price feeds that originate from pythtest-crosschain.

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.

Deployment

Deploying the CosmWasm contract has three steps:

  1. Upload the code. This step will give you a code id.
  2. Either create a new contract or upgrade an existing one:
    1. Create a new contract that has an address with a code id as its program.
    2. Upgrade an existing contract code id to the new code id using governance messages.
  3. Update contract's admin to itself.

The scripts directory contains the instructions and scripts to perform all the steps.

Permissoned networks:

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.