Package 0xadcc…daae
Package0xadcc…daae
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x30ed…fc88Address0x30edcc71bffecab211665e4f22cac737de7ca0d734256e86b70dc7e168cefc88LabelNone known
- Package ID
- 0xadcc…daae
- 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
- 0xcf04…aed2Object0xcf046a9f36fcb81d9dd9b9bb3d690c28b22aaa7f8211921424b23cea2075aed2
- Cap holder
- 0x30ed…fc88Address0x30edcc71bffecab211665e4f22cac737de7ca0d734256e86b70dc7e168cefc88LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0106248 SUI
- Publish tx
- AzmVSR…kiPe
Modules
2 functions, 1 public, 3 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| commemorative_nfts | 1 | 0 | 3 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xadcc…daae, 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 | 0xadcc…daae | 0x30ed…fc88Address0x30edcc71bffecab211665e4f22cac737de7ca0d734256e86b70dc7e168cefc88LabelNone known | AzmVSR…kiPe | … |
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 | 4 | |
| Sui Framework | 0x0000…0002 | Same | 19 |