Package 0x01d4…edca
Package0x01d4…edca
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x1ce1…0ae9Address0x1ce122f117c693316f8c7b9aec1e339088ea1fcc496dd5ddad08118aec920ae9LabelNone known
- Package ID
- 0x01d4…edca
- 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
- 0x79c0…c250Object0x79c009e20c3b844d621d473eede12600c28e3425caeb3890ddf93d08d85cc250
- Cap holder
- 0x1ce1…0ae9Address0x1ce122f117c693316f8c7b9aec1e339088ea1fcc496dd5ddad08118aec920ae9LabelNone known
- Source
- Not verified
- Storage deposit
- 0.2670412 SUI
- Publish tx
- 3J15MW…hHnq
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) 0x01d4…edca, 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 | 0x01d4…edca | 0x1ce1…0ae9Address0x1ce122f117c693316f8c7b9aec1e339088ea1fcc496dd5ddad08118aec920ae9LabelNone known | 3J15MW…hHnq | … |
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 | 9 | |
| Sui Framework | 0x0000…0002 | Same | 27 |