You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Transparency: Users can understand the update potential of a module
Security Assessment: Developers can quickly evaluate the immutability of critical contracts
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.
The text was updated successfully, but these errors were encountered:
🚀 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
orcompatible
) 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:
Importance of This Feature
Showing the upgrade policy is crucial for:
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.
The text was updated successfully, but these errors were encountered: