Package 0x4a6d…80ab
Package0x4a6d…80ab
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xdd71…c2ecAddress0xdd7126a71c9c29145dd71bd28ef0db7d986cde112641d4b659e8144d86e9c2ecLabelNone known
- Package ID
- 0x4a6d…80ab
- Published
- Upgrade policy
Compatible?
The holder of the upgrade cap can publish new versions. A new version must keep every public function signature and struct layout, so existing callers keep working.
- Upgrade cap
- 0x7d94…7700Object0x7d942eab1a3d972c8118d5a9d13b910d6eab6ba9b422b89abccf61f8ace97700
- Cap holder
- 0xdd71…c2ecAddress0xdd7126a71c9c29145dd71bd28ef0db7d986cde112641d4b659e8144d86e9c2ecLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0096064 SUI
- Publish tx
- 5hp6Pq…CWBu
Modules
1 functions, 0 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x4a6d…80ab, and the version number counts up, so the highest number is the current code.
A transaction names the exact package ID it calls, so older versions can still be called unless the package itself refuses them, often with a version check on a shared object.
A type keeps the ID of the version that first defined it. Types from version 1 use the original ID for good, while a type added in a later upgrade uses that version's ID.
| Version | Package ID | Time | By | Transaction | Calls, 7 days | |
|---|---|---|---|---|---|---|
| Version 1LatestPublished | 0x4a6d…80ab | 0xdd71…c2ecAddress0xdd7126a71c9c29145dd71bd28ef0db7d986cde112641d4b659e8144d86e9c2ecLabelNone known | 5hp6Pq…CWBu | … |
Recent calls
No calls to this package found
Dependencies
The exact versions this package was linked against
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 25 | |
| Sui Framework | 0x0000…0002 | Same | 59 |