verify-package

Downloads a Package and Verifies the Bytecode

Downloads the package from on-chain and verifies the bytecode matches a local compilation of the Move code.

Usage

movement aptos move verify-package [OPTIONS] --account <ACCOUNT>

Options

• --account <ACCOUNT> Address of the account containing the package.

• --included-artifacts <INCLUDED_ARTIFACTS> Artifacts to be generated when building this package. [default: sparse] [possible values: none, sparse, all]

• --dev Enables dev mode, which uses all dev-addresses and dev-dependencies. Dev mode allows for changing dependencies and addresses to the preset [dev-addresses] and [dev-dependencies] fields. This works both inside and out of tests for using preset values. Currently, it also additionally pulls in all test compilation artifacts.

• --package-dir <PACKAGE_DIR> Path to a move package (the folder with a Move.toml file).

• --output-dir <OUTPUT_DIR> Path to save the compiled move package. Defaults to <package_dir>/build.

• --named-addresses <NAMED_ADDRESSES> Named addresses for the move binary. Example: alice=0x1234, bob=0x5678. Note: This will fail if there are duplicates in the Move.toml file remove those first. [default: ]

• --skip-fetch-latest-git-deps Skip pulling the latest git dependencies. This will allow overriding this for local development.

• --bytecode-version <BYTECODE_VERSION> Specify the version of the bytecode the compiler is going to emit.

• --url <URL> URL to a fullnode on the network. Defaults to the URL in the default profile.

• --connection-timeout-secs <CONNECTION_TIMEOUT_SECS> Connection timeout in seconds, used for the REST endpoint of the fullnode. [default: 30]

• --profile <PROFILE> Profile to use from the CLI config. This will be used to override associated settings such as the REST URL, the Faucet URL, and the private key arguments. Defaults to "default".