verify-proposal

Verify a Proposal Given the Source Code of the Script

The script's bytecode or source can be provided and it will verify whether the hash matches the onchain hash.

Usage

movement aptos governance verify-proposal [OPTIONS] --proposal-id <PROPOSAL_ID>

Options

• --proposal-id <PROPOSAL_ID> The id of the onchain proposal

• --script-path <SCRIPT_PATH> Path to the Move script for the proposal

• --compiled-script-path <COMPILED_SCRIPT_PATH> Path to the Move script for the proposal

• --framework-git-rev <FRAMEWORK_GIT_REV> Git revision or branch for the Aptos framework. This is mutually exclusive with --framework-local-dir

• --framework-local-dir <FRAMEWORK_LOCAL_DIR> Local framework directory for the Aptos framework. This is mutually exclusive with --framework-git-rev

• --skip-fetch-latest-git-deps Skip pulling the latest git dependencies. If you don't have a network connection, the compiler may fail due to no ability to pull git dependencies. This will allow overriding this for local development.

• --bytecode-version <BYTECODE_VERSION>

• --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"

• --assume-yes Assume yes for all yes/no prompts

• --assume-no Assume no for all yes/no prompts