GitBross Accueil Explorer Aide
S'inscrire Connexion
sol_BMCMMXZh
/
pyth-network_pyth-crosschain
miroir de https://github.com/pyth-network/pyth-crosschain
1
0
Fork 0
Fichiers Tickets 1 Wiki
Branche: devin/1738952382-move-pythnet-sdk
Branches Tags
pyth-network_py...
/
target_chains
/
cosmwasm
Devin AI 419e180538 refactor: update remaining pythnet-sdk paths il y a 9 mois
..
contracts 419e180538 refactor: update remaining pythnet-sdk paths il y a 9 mois
deploy-scripts 51d5217a57 Fix workspace references il y a 1 an
devnet 084acdb57e [refactor] Convert hyphen to underscore in the directory tree (#524) il y a 2 ans
examples 955a805e85 chore: apply rustfmt il y a 1 an
sdk 1e692e1de2 Deny clippy warnings in CI properly (#2109) il y a 1 an
tools f1c8493118 feat: added gas multiplier arg for injective (#2104) il y a 1 an
wormhole-stub e5fd5a9d81 [target_chains] Add deployment information for neutron mainnet (#930) il y a 2 ans
.gitignore 079828f8ac Wormhole stub (#789) il y a 2 ans
Cargo.lock 0a0257e2fe fix(rust): update cargo.lock files after pythnet sdk release (#2111) il y a 1 an
Cargo.toml e1db4aad65 [rust] Remove serde_wormhole patch (#1249) il y a 1 an
README.md a7d133d063 [cosmwasm] CosmWasm integration with contract manager (#1025) il y a 2 ans

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.