The example package publish tx failed with error 'PublishUpgradeMissingDependency in command 0'

[ws4charlie]

The sui example package publish tx failed with below errors in the sui client publish CLI

Failed to publish the Move module(s), reason: [warning] Multiple source verification errors found:

- On-chain version of dependency gateway::evm was not found.
- On-chain version of dependency gateway::gateway was not found.
- Local version of dependency 4496908a03cd710d7bcb2a98c959e4b2a1eff224dce6e9ce6a941aa9e4e500f4::evm was not found.
- Local version of dependency 4496908a03cd710d7bcb2a98c959e4b2a1eff224dce6e9ce6a941aa9e4e500f4::gateway was not found.

This may indicate that the on-chain version(s) of your package's dependencies may behave differently than the source version(s) your package was built against.

Fix this by rebuilding your packages with source versions matching on-chain versions of dependencies, or ignore this warning by re-running with the --skip-dependency-verification flag.

If we add --skip-dependency-verification flag, the publish failed in Sui explorer like below

[ws4charlie]

Two experiments were done on Sui example package deployment, and the above error can be replicated.

The sui CLI binary 1.59.1 was used across all experiments (for sui move build, sui client upgrade, sui client publish), so version is not a issue.

Experiment 1: (deploy fresh v2 package, without upgrade, then deploy example package):

step-1. Checkout the new release (v2) of the gateway package repo. Then I deployed it to testnet and got package ID 0x7814673d7c5df6c9ab321e37172ef1bd4d243837b6017ed2b7938a3982a3080e

step-2. Grab the example package in V37 node repo, and I pointed it to the newly deployed gateway package ID in Move.toml file. To achieve this, the [dependencies] section in example Move.toml should point to correct source of gateway v2 package. For example:
gateway = { git = "https://github.com/zeta-chain/protocol-contracts-sui.git", rev = "some-v2-deployment-commit-hash" }

step-3. The example package got compiled and deployed successfully.

Result: This experiment was simple, without gateway package upgrade, so deployment was smooth.

Experiment 2: (upgrade from v1 to v2, then deploy example package):

step-1. Checkout the old release (v1) of the gateway package repo. Then I deployed it to testnet and got package ID 0x4496908a03cd710d7bcb2a98c959e4b2a1eff224dce6e9ce6a941aa9e4e500f4

step-2. Checkout the new release (v2) of the gateway package repo. Then I compiled it and upgraded the v1 package (in step 1) to v2, resulting a new package ID 0x99578573550ef52ef4f1b0682fa5b822caedca3453f9d4c9bb48559f43ebcfa1

step-3. Grab the example package in V37 node repo, and I pointed it to the upgraded gateway package ID (in step 2) in Move.toml file. To achieve this, the [dependencies] section in example Move.toml should point to correct source of gateway v2 package. For example:
gateway = { git = "https://github.com/zeta-chain/protocol-contracts-sui.git", rev = "some-v2-upgrade-commit-hash" }

step-4. The example package got compiled without issue. But the deployment failed with below error:

Failed to publish the Move module(s), reason: [warning] Multiple source verification errors found:
 On-chain version of dependency gateway::gateway was not found.
 On-chain version of dependency gateway::evm was not found.
 Local version of dependency 4496908a03cd710d7bcb2a98c959e4b2a1eff224dce6e9ce6a941aa9e4e500f4::gateway was not found.
 Local version of dependency 4496908a03cd710d7bcb2a98c959e4b2a1eff224dce6e9ce6a941aa9e4e500f4::evm was not found.

Result: Although the example got compiled, but the dependency verification will fail in publish tx.

To summarize:

The only difference between above two experiments was:

• Experiment 1 ✅: no upgrade in between
• Experiment 2 ❌: upgrade from v1 to v2 in between

[lumtis]

In #70

I can run sui client publish

If I remove this line in the move.toml

[addresses]
example = "0x0"
# gateway = "0x0"