benduran 31c364cf41 feat: performed a minor bump all packages, since all were changed in the big dual package update		2 minggu lalu
..
src	8c57372132 fix(pyth-iota-cli): fixed build	3 minggu lalu
.gitignore	ab0cf6f7d8 chore: updated gitignore to excluse the built dist/ folder	3 minggu lalu
.prettierignore	6efbe89542 chore: updated prettier ignores to prevent bikeshedding	2 minggu lalu
README.md	f61d4dd546 feat(target_chains/sui): add iota network (#2428)	8 bulan lalu
package.json	31c364cf41 feat: performed a minor bump all packages, since all were changed in the big dual package update	2 minggu lalu
tsconfig.build.json	87679545bb chore: removed npm-specific things and removed more packageManager fields	2 minggu lalu
tsconfig.json	fe92275443 chore: migrated all package.json and tsconfig files to a single, modern standard	3 minggu lalu

Pre-requisites

Install move cli according to this doc

Deploying from scratch

Configure the Move.toml file accordingly. The wormhole address should be specified based on the target chain in the Move.toml and the pyth address should be 0x0. We can deploy the pyth oracle and initialize it with the following command:

npm run cli -- deploy --private-key <private-key> --chain [iota_sui|iota_sui]

You can then add your iota contract configs to the contract manager store.

You can also manually create all the price feeds available at the moment to make it easier for devs to test the oracle.

npm run cli -- create-all --private-key <private-key> --contract <contract-id>

Updating price feeds:

You can use the create and update-feeds commands to create and update price feeds respectively.

npm run cli -- create --feed-id <feed-id> --private-key <private-key> --contract <contract-id>

npm run cli -- update-feeds --feed-id <feed-id> --private-key <private-key> --contract <contract-id>

Upgrade process:

The following steps are needed to upgrade our iota contracts:

Contract changes:
- Create a new struct for the new version and update current_version and previous_version functions in version_control module
- Implement any custom logic needed to migrate the data from the old struct to the new one in the migrate module
- Update dependency (e.g. wormhole) addresses if needed
Generate the digest for the new contract build
Create a governance proposal, proposing the iota package to be upgraded to this specific digest
Approve and execute the governance proposal
Run the upgrade transaction and publish the new package

Generating the new contract hash:

Run the following command to generate the new hash, make sure the contract addresses are identical to the deployed ones:

npm run cli -- generate-digest

Upgrading the contract

To upgrade the contract after the governance vaa was executed run:

npm run cli -- upgrade --private-key <private-key> --contract <contract-id> --vaa <upgrade-vaa>

The upgrade procedure consists of 2 transactions. The first one is to upgrade the contract (iota level) and the second one is to run the migrate function and upgrade the version (package level). Since clients try to fetch the latest version of the package automatically, it's important to run the second transaction as soon as possible after the first one.

FAQ:

I'm seeing the error Transaction has non recoverable errors from at least 1/3 of validators. What should I do? Make sure you have enough funding in the wallet and try again. Usually a more descriptive error message is available in the returned value of the transaction.

README.md