Package 0x2ad2…1a7d
Package0x2ad2…1a7d
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x79d1…a5eeAddress0x79d1158831e9e80ff3f5be6be8b7350d089abae3e87c8ec4ce327c183dada5eeLabelNone known
- Package ID
- 0x2ad2…1a7d
- 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
- 0x9163…5282Object0x9163d6439b460b301d105c636e627f97e324596e5fefd06643fdccc952955282
- Cap holder
- 0x79d1…a5eeAddress0x79d1158831e9e80ff3f5be6be8b7350d089abae3e87c8ec4ce327c183dada5eeLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0071972 SUI
- Publish tx
- H4YhqN…75VU
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) 0x2ad2…1a7d, 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 | 0x2ad2…1a7d | 0x79d1…a5eeAddress0x79d1158831e9e80ff3f5be6be8b7350d089abae3e87c8ec4ce327c183dada5eeLabelNone known | H4YhqN…75VU | … |
Recent calls
Reading recent calls
Dependencies
The exact versions this package was linked against
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |