Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Add Upgrade Policy Visibility for Modules in Explorer #949

Open
mshakeg opened this issue Dec 1, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@mshakeg
Copy link

mshakeg commented Dec 1, 2024

🚀 Feature Request Description

Is your feature request related to a problem? Please describe your use case.

When examining modules on the Aptos Explorer, users currently cannot determine the upgrade policy (immutable or compatible) of a published module. This lack of information creates uncertainty about the module's potential for future modifications and its long-term stability.

Expected Behavior

Add a clearly visible indicator next to each module that shows its upgrade policy. This could be:

  • A small badge or icon
  • A text label
  • A tooltip with the specific upgrade policy details

Importance of This Feature

Showing the upgrade policy is crucial for:

  1. Transparency: Users can understand the update potential of a module
  2. Security Assessment: Developers can quickly evaluate the immutability of critical contracts
  3. Trust Verification: Stakeholders can confirm whether a module can be changed in the future

Additional context

The upgrade policy information is typically defined in the Move.toml manifest and checked during module publication, so this information should be readily available.

Describe alternatives you've considered

N/A

Are you willing to open a pull request?

Unfortunately not.

@mshakeg mshakeg added the enhancement New feature or request label Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant