• go.mod is excluded by: !**/*.mod
• go.sum is excluded by: !**/*.sum
• proto/buf.gen.pulsar.yaml is excluded by: !**/*.yaml

• .github/workflows/TestUnit.yml (1 hunks)
• Dockerfile (1 hunks)
• Makefile (2 hunks)
• app/ante/handler_options.go (1 hunks)
• app/app.go (1 hunks)
• app/encoding.go (1 hunks)
• app/genesis.go (1 hunks)
• app/keepers/keepers.go (1 hunks)
• app/keepers/keys.go (1 hunks)
• app/modules.go (1 hunks)
• app/rpc/auth.go (1 hunks)
• app/rpc/override.go (1 hunks)
• app/sim_test.go (3 hunks)
• app/upgrade.go (1 hunks)
• app/upgrades/types.go (1 hunks)
• app/upgrades/v200/config.go (1 hunks)
• app/upgrades/v200/upgrades.go (1 hunks)
• app/upgrades/v210/upgrades.go (1 hunks)
• app/upgrades/v300/upgrades.go (1 hunks)
• client/lite/swagger.go (1 hunks)
• cmd/iris/cmd/genesis.go (1 hunks)
• cmd/iris/cmd/keys.go (1 hunks)
• cmd/iris/cmd/root.go (1 hunks)
• cmd/iris/cmd/testnet.go (1 hunks)
• cmd/iris/main.go (1 hunks)
• modules/guardian/client/cli/cli_test.go (1 hunks)
• modules/guardian/client/cli/query.go (1 hunks)
• modules/guardian/client/cli/tx.go (1 hunks)
• modules/guardian/client/testutil/test_helpers.go (1 hunks)
• modules/guardian/genesis.go (1 hunks)
• modules/guardian/genesis_test.go (1 hunks)
• modules/guardian/handler.go (1 hunks)
• modules/guardian/keeper/grpc_query.go (1 hunks)
• modules/guardian/keeper/grpc_query_test.go (1 hunks)
• modules/guardian/keeper/keeper.go (1 hunks)
• modules/guardian/keeper/keeper_test.go (1 hunks)
• modules/guardian/keeper/msg_service.go (1 hunks)
• modules/guardian/module.go (1 hunks)
• modules/guardian/types/msgs_test.go (2 hunks)
• modules/mint/abci.go (1 hunks)
• modules/mint/abci_test.go (1 hunks)
• modules/mint/client/cli/cli_test.go (1 hunks)
• modules/mint/client/cli/query.go (1 hunks)
• modules/mint/client/rest/grpc_query_test.go (1 hunks)
• modules/mint/client/testutil/test_helpers.go (1 hunks)
• modules/mint/genesis.go (1 hunks)
• modules/mint/keeper/grpc_query.go (1 hunks)
• modules/mint/keeper/grpc_query_test.go (1 hunks)
• modules/mint/keeper/keeper.go (1 hunks)
• modules/mint/keeper/keeper_test.go (1 hunks)
• modules/mint/keeper/migrations.go (1 hunks)
• modules/mint/keeper/msg_server.go (1 hunks)
• modules/mint/keeper/params.go (1 hunks)
• modules/mint/migrations/v2/migrate.go (1 hunks)
• modules/mint/module.go (1 hunks)
• modules/mint/simulation/decoder.go (1 hunks)
• modules/mint/simulation/decoder_test.go (1 hunks)
• modules/mint/simulation/genesis.go (1 hunks)
• proto/irishub/guardian/genesis.proto (1 hunks)
• proto/irishub/guardian/guardian.proto (1 hunks)
• proto/irishub/guardian/query.proto (1 hunks)
• proto/irishub/guardian/tx.proto (1 hunks)
• proto/irishub/mint/genesis.proto (1 hunks)
• proto/irishub/mint/mint.proto (1 hunks)
• proto/irishub/mint/query.proto (1 hunks)
• proto/irishub/mint/tx.proto (1 hunks)
• scripts/protocgen.sh (1 hunks)
• simapp/app.go (2 hunks)
• simapp/test_helpers.go (1 hunks)
• sims.mk (1 hunks)

• .github/workflows/TestUnit.yml
• app/upgrade.go

app/genesis.go (1)

• 4-4: The update of the import path from v2 to v3 for the types package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

proto/irishub/guardian/genesis.proto (1)

• 7-7: Updating the go_package option from v2 to v3 is crucial for the correct generation of Go code from protobuf definitions. Ensure that the generated code is correctly placed in the new package version and is compatible with the rest of the project.

proto/irishub/mint/genesis.proto (1)

• 7-7: The update of the go_package option from v2 to v3 ensures that the generated Go code from protobuf definitions is correctly placed in the new package version. Verify that the generated code is compatible with the rest of the project.

modules/mint/keeper/grpc_query.go (1)

• 8-8: The update of the import path from v2 to v3 for the types package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

cmd/iris/main.go (1)

• 9-11: The updates of import paths from v2 to v3 for multiple packages are aligned with the PR's objectives. Ensure that the new versions of the packages are fully compatible with the current usage in the project.

client/lite/swagger.go (1)

• 11-11: The update of the import path from v2 to v3 for the statik package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

app/encoding.go (1)

• 6-6: The update of the import path from v2 to v3 for the params package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

modules/mint/client/testutil/test_helpers.go (1)

• 12-12: The update of the import path from v2 to v3 for the mintcli package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

modules/mint/migrations/v2/migrate.go (1)

• 8-8: The update of the import path from v2 to v3 for the types package is aligned with the PR's objectives. Ensure that the new version of the package is fully compatible with the current usage in the project.

Dockerfile (1)

• 4-4: Updating the base image to golang:1.21-alpine is aligned with the PR's objectives to use a current and supported version of Go. Ensure that the new base image is fully compatible with the project's build requirements and does not introduce any issues.

modules/mint/keeper/grpc_query_test.go (1)

• 8-8: The import path for the types package has been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3.

modules/mint/keeper/migrations.go (1)

• 8-8: The import path for the migration package has been correctly updated from v2 to v3, which is consistent with the PR's goal of updating import paths to reflect the new versioning.

modules/mint/simulation/decoder.go (1)

• 10-10: The import path for the types package has been updated from v2 to v3, aligning with the PR's objective. This change is crucial for ensuring that the simulation decoder uses the correct version of the types package.

app/rpc/override.go (1)

• 7-7: The import path for the keepers package has been correctly updated from v2 to v3. This change is essential for ensuring that the RPC override functionality uses the updated keepers package.

modules/mint/keeper/params.go (1)

• 6-6: The import path for the types package has been updated from v2 to v3, which is in line with the PR's goal of migrating to version 3. This update is crucial for ensuring that the mint module's parameter handling functions use the correct types.

proto/irishub/guardian/guardian.proto (1)

• 6-6: The go_package option has been correctly updated from v2 to v3 in the guardian.proto file. This change is essential for ensuring that the generated Go code from protobuf definitions aligns with the updated import paths.

proto/irishub/mint/query.proto (1)

• 9-9: The go_package option has been updated from v2 to v3 in the query.proto file, which is consistent with the PR's objective of migrating to version 3. This update ensures that the generated Go code for the mint module's query service uses the correct version of the types package.

scripts/protocgen.sh (1)

• 22-22: The directory path in the protocgen.sh script has been correctly updated from v2 to v3. This change ensures that the generated protobuf code is placed in the correct directory, aligning with the new versioning scheme.

modules/guardian/keeper/grpc_query_test.go (1)

• 9-9: The import path for the types package has been correctly updated from v2 to v3 in the guardian module's test file. This update is crucial for ensuring that the test function uses the correct version of the types package.

proto/irishub/guardian/tx.proto (1)

• 4-4: The go_package option in the tx.proto file has been correctly updated from v2 to v3. This change ensures that the generated Go code for the guardian module's transaction messages aligns with the updated import paths.

modules/guardian/handler.go (1)

• 7-8: The import paths for guardian/keeper and guardian/types have been updated from v2 to v3. This change aligns with the PR's objective to migrate to version 3 of the software. Ensure that all references to these packages elsewhere in the project have also been updated to maintain consistency and avoid import errors.

proto/irishub/mint/mint.proto (1)

• 7-7: The go_package option has been updated to reflect the new version path, moving from v2 to v3. This change is essential for ensuring that the generated Go code is consistent with the updated import paths throughout the project. Verify that all protobuf files in the project have been similarly updated to maintain consistency.

proto/irishub/guardian/query.proto (1)

• 9-9: The go_package option has been updated to github.com/irisnet/irishub/v3/modules/guardian/types, moving from v2 to v3. This update is crucial for the correct generation of Go code from protobuf definitions and maintaining consistency with the updated import paths throughout the project. Ensure that all related protobuf files have been similarly updated.

modules/mint/keeper/msg_server.go (1)

• 9-9: The import path for the types package has been updated from v2 to v3. This change is part of the broader effort to migrate to version 3 of the software and ensures that the mint module's message handling is compatible with the updated version. Confirm that all references to the mint module's types package elsewhere in the project have also been updated to maintain consistency.

modules/guardian/keeper/grpc_query.go (1)

• 12-12: The import path for the types package has been updated from v2 to v3. This change ensures that the guardian module's gRPC query handling is compatible with the updated version. It's important to verify that all references to the guardian module's types package elsewhere in the project have also been updated to maintain consistency and avoid import errors.

modules/guardian/genesis_test.go (1)

• 13-16: The import paths for modules related to guardian have been updated from v2 to v3. This update is essential for ensuring that the tests are aligned with the updated version of the software and that they accurately reflect the current state of the guardian module. Confirm that all related tests and modules have been similarly updated to maintain consistency.

modules/mint/simulation/decoder_test.go (1)

• 13-15: The import paths for modules related to minting have been updated from v2 to v3. This update is essential for ensuring that the tests are aligned with the updated version of the software and that they accurately reflect the current state of the mint module. Confirm that all related tests and modules have been similarly updated to maintain consistency.

modules/mint/simulation/genesis.go (1)

• 13-13: The import path for the mint/types package has been updated from irishub/v2 to irishub/v3. This change is crucial for ensuring that the simulation functionality is aligned with the updated version of the software. It's important to verify that all related simulation files and modules have been similarly updated to maintain consistency.

app/upgrades/v200/config.go (1)

• 9-9: The import statement for the types package has been updated from irishub/v2 to irishub/v3. This change is part of the broader effort to migrate to version 3 of the software and ensures that the upgrade configuration is compatible with the updated version. Confirm that all references to the types package elsewhere in the project have also been updated to maintain consistency.

modules/mint/genesis.go (1)

• 7-8: The import paths for keeper and types have been updated from v2 to v3. This change is crucial for ensuring that the mint module's genesis functionality is aligned with the updated version of the software. It's important to verify that all related files and modules have been similarly updated to maintain consistency.

modules/guardian/genesis.go (1)

• 8-9: The import paths for the guardian module have been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3.

proto/irishub/mint/tx.proto (1)

• 9-9: The go_package option in the tx.proto file has been correctly updated to reflect the migration from v2 to v3 for the mint module. This change is crucial for ensuring that the generated Go code aligns with the updated import paths.

modules/mint/abci_test.go (1)

• 13-15: The import paths for the mint and simapp packages have been correctly updated from v2 to v3. This change is part of the broader effort to migrate the project to version 3, ensuring compatibility and leveraging improvements.

modules/mint/client/cli/query.go (1)

• 11-11: The import path for the mint/types package has been correctly updated to v3, aligning with the PR's objective to migrate to version 3. This ensures that the CLI commands for the mint module will function correctly with the updated module version.

modules/mint/client/cli/cli_test.go (1)

• 10-12: The import paths for minttestutil, minttypes, and simapp have been correctly updated from v2 to v3. This ensures that the integration tests for the mint CLI commands will function correctly with the updated module version.

modules/guardian/client/cli/query.go (1)

• 13-13: The import path for the types package of the guardian module has been correctly updated to v3, aligning with the PR's objective to migrate to version 3. This ensures that the CLI commands for the guardian module will function correctly with the updated module version.

modules/guardian/client/testutil/test_helpers.go (1)

• 16-17: The import paths for the guardiancli package and the simapp package have been correctly updated from v2 to v3. This ensures that the test utilities for the guardian module will function correctly with the updated module version.

modules/mint/abci.go (1)

• 6-7: The import paths for the mint/keeper and mint/types packages have been correctly updated from v2 to v3. This ensures that the BeginBlocker function for the mint module will function correctly with the updated module version.

modules/mint/client/rest/grpc_query_test.go (1)

• 13-14: The import paths for minttypes and simapp have been correctly updated from v2 to v3. This ensures that the GRPC query tests for the mint module will function correctly with the updated module version.

app/upgrades/v210/upgrades.go (1)

• 16-16: The import path for the upgrades package has been correctly updated to v3, aligning with the PR's objective to migrate to version 3. This ensures that the upgrade logic will function correctly with the updated module version.

app/upgrades/v300/upgrades.go (1)

• 15-15: The import path for upgrades has been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3. This change is crucial for maintaining compatibility with the new versioning scheme and leveraging the latest features and improvements.

modules/guardian/keeper/keeper.go (1)

• 12-12: The import path for the types package within the guardian module has been correctly updated from v2 to v3. This change ensures that the guardian module is compatible with the new versioning scheme and can utilize the latest features and improvements introduced in version 3.

app/upgrades/types.go (1)

• 12-12: The import path for the keepers package has been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3. This change is crucial for ensuring that the upgrades package remains compatible with the new versioning scheme and can leverage the latest features and improvements.

modules/mint/keeper/keeper.go (1)

• 12-12: The import path for the types package within the mint module has been correctly updated from v2 to v3. This change ensures that the mint module is compatible with the new versioning scheme and can utilize the latest features and improvements introduced in version 3.

modules/guardian/keeper/keeper_test.go (1)

• 16-18: The import paths for modules related to guardian functionality have been correctly updated from v2 to v3. This change ensures that the guardian module's tests are compatible with the new versioning scheme and can leverage the latest features and improvements introduced in version 3.

modules/guardian/keeper/msg_service.go (1)

• 9-9: The import path for the types package within the guardian module has been correctly updated from v2 to v3. This change ensures that the guardian module's message service is compatible with the new versioning scheme and can utilize the latest features and improvements introduced in version 3.

modules/guardian/client/cli/tx.go (1)

• 13-13: The import path for the types package within the guardian module has been correctly updated from v2 to v3. This change ensures that the guardian module's CLI commands are compatible with the new versioning scheme and can utilize the latest features and improvements introduced in version 3.

app/upgrades/v200/upgrades.go (1)

• 21-22: The import paths for upgrades and irisevm have been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3. These changes are crucial for ensuring compatibility with the new versioning scheme and leveraging the latest features and improvements.

modules/mint/keeper/keeper_test.go (1)

• 15-16: The import paths for mint/types and simapp have been correctly updated from v2 to v3. These changes ensure that the mint module's tests are compatible with the new versioning scheme and can leverage the latest features and improvements introduced in version 3.

app/rpc/auth.go (1)

• 22-22: The import path for the keepers package has been correctly updated from v2 to v3, aligning with the PR's objective to migrate to version 3. This change is crucial for ensuring that the auth RPC functionality remains compatible with the new versioning scheme and can leverage the latest features and improvements.

sims.mk (1)

• 7-7: The update of the import path from v2 to v3 aligns with the PR objectives of migrating to a newer version. This change is crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to this package throughout the project have been updated accordingly to prevent any build or runtime errors.

modules/guardian/types/msgs_test.go (1)

• 13-13: The update of the import path from v2 to v3 aligns with the PR objectives of migrating to a newer version. This change is crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to this package throughout the project have been updated accordingly to prevent any build or runtime errors.

cmd/iris/cmd/keys.go (1)

• 21-21: The update of the import path from v2 to v3 aligns with the PR objectives of migrating to a newer version. This change is crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to this package throughout the project have been updated accordingly to prevent any build or runtime errors.

cmd/iris/cmd/genesis.go (1)

• 19-19: The update of the import path from v2 to v3 aligns with the PR objectives of migrating to a newer version. This change is crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to this package throughout the project have been updated accordingly to prevent any build or runtime errors.

modules/guardian/client/cli/cli_test.go (1)

• 18-21: The updates of the import paths from v2 to v3 align with the PR objectives of migrating to a newer version. These changes are crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to these packages throughout the project have been updated accordingly to prevent any build or runtime errors.

app/ante/handler_options.go (1)

• 17-17: The update of the import path from v2 to v3 aligns with the PR objectives of migrating to a newer version. This change is crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to this package throughout the project have been updated accordingly to prevent any build or runtime errors.

app/keepers/keys.go (1)

• 44-45: The updates of the import paths from v2 to v3 align with the PR objectives of migrating to a newer version. These changes are crucial for ensuring compatibility with the latest features and improvements introduced in version 3. Ensure that all references to these packages throughout the project have been updated accordingly to prevent any build or runtime errors.

modules/guardian/module.go (1)

• 21-23: The import paths for the guardian module have been updated from v2 to v3, aligning with the PR's objective to migrate to version 3. This change is correctly applied and consistent with the project's migration strategy. Ensure that all references to these packages elsewhere in the project have been similarly updated to avoid import errors.

modules/mint/module.go (1)

• 22-25: The import paths for the mint module have been updated from v2 to v3, which is in line with the PR's goal of transitioning to version 3. These changes are correctly implemented and consistent across the file. It's important to verify that all references to these packages throughout the project have been updated accordingly to maintain compatibility.

cmd/iris/cmd/root.go (1)

• 34-36: The import paths in cmd/iris/cmd/root.go have been updated from v2 to v3, consistent with the overarching goal of migrating to version 3. These changes are correctly applied and ensure that the CLI tooling is aligned with the new versioning. As with other modules, confirm that all references to these packages across the project have been updated to prevent import errors.

Makefile (2)

• 63-63: Change looks good and aligns with the PR objectives of migrating to version 3.
• 196-202: The adjustments to the formatting commands to include the client directory seem appropriate. Please ensure the new path exists and is correct.

Verification successful

---

The verification process confirms the existence of the client directory within the project, supporting the adjustments made to the formatting commands in the Makefile. It's advisable to ensure the specific paths used in the commands are correct, but the presence of the client directory aligns with the changes made.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the existence of the new path in the formatting commands.
if fd --type d "client" .; then
  echo "The client directory exists."
else
  echo "The client directory does not exist. Please check the path."
  exit 1
fi

Length of output: 168

app/app.go (1)

• 38-43: The update of import paths from v2 to v3 for various modules aligns with the PR objectives. Please ensure the correctness of the new import paths and that the referenced modules exist in version 3.

Verification successful

---

The verification process confirms that the updated import paths from v2 to v3 for the specified modules (ante, keepers, params, rpc, lite, types) are correct and that these modules exist in version 3 of the irishub repository. This aligns with the PR objectives and supports the approval of these changes.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the existence of the updated modules in version 3.
MODULES=("ante" "keepers" "params" "rpc" "lite" "types")
for module in "${MODULES[@]}"; do
  if fd --type d "irishub/v3/app/${module}" .; then
    echo "The ${module} module exists in version 3."
  else
    echo "The ${module} module does not exist in version 3. Please check the import path."
    exit 1
  fi
done

Length of output: 979

simapp/test_helpers.go (1)

• 46-47: The update of import paths for minttypes and iristypes from v2 to v3 aligns with the PR objectives. Please ensure the correctness of the new import paths and that the referenced modules exist in version 3.

Verification successful

---

The verification process confirms that the updated import paths for minttypes and iristypes to version 3 are correct, as both mint/types and types modules exist in irishub/v3/modules. This aligns with the PR objectives and confirms the accuracy of the review comment.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the existence of the updated modules in version 3.
MODULES=("mint/types" "types")
for module in "${MODULES[@]}"; do
  if fd --type d "irishub/v3/modules/${module}" .; then
    echo "The ${module} module exists in version 3."
  else
    echo "The ${module} module does not exist in version 3. Please check the import path."
    exit 1
  fi
done

Length of output: 363

app/sim_test.go (1)

• 22-22: The update of the import path for iristypes from v2 to v3 aligns with the PR's objectives to migrate to version 3. This change is correctly implemented.

cmd/iris/cmd/testnet.go (1)

• 48-49: The update of the import paths for guardiantypes and iristypes from v2 to v3 aligns with the PR's objectives to migrate to version 3. These changes are correctly implemented.

app/modules.go (4)

• 88-88: The update of the irisappparams import path to include /v3/ aligns with the PR objectives of migrating from v2 to v3. This change appears correct.
• 89-89: The update of the irisevm import path to include /v3/ is consistent with the PR's goal of migrating to version 3. This change is correctly implemented.
• 90-91: The updates to the guardian and guardiantypes import paths to include /v3/ are appropriate and align with the PR's migration to version 3. These changes are correctly implemented.
• 92-93: The updates to the mint and minttypes import paths to include /v3/ are correctly implemented and align with the PR's objective of migrating to version 3.

simapp/app.go (1)

• 67-74: The import paths for irishub modules have been updated from v2 to v3, aligning with the PR's objective to migrate to version 3. This change is crucial for ensuring compatibility with the new version and leveraging improvements and features introduced in version 3. Ensure that all references to these modules elsewhere in the codebase are also updated to reflect this change.

app/keepers/keepers.go (2)

• 108-113: The import paths for guardian, mint, and types modules have been correctly updated from v2 to v3, aligning with the PR objectives to migrate to version 3 of irishub. This change is crucial for ensuring compatibility with the new version and leveraging the latest features and improvements.
• 108-113: The changes to the import paths for the guardian and mint modules are correctly reflected in the AppKeepers struct. It's important to ensure that the rest of the codebase, especially where these keepers are utilized, is updated accordingly to avoid any compatibility issues with the new versioning.