Package 0x468b…5d5c
Package0x468b…5d5c
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x32f2…e3ceAddress0x32f205839784554db3ae9fcafecb26c6cdbd4903b4033b2407d5647b9e63e3ceLabelNone known
- Package ID
- 0x468b…5d5c
- 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
- 0xcbe6…b4f8Object0xcbe6e8c3eb417a02e783d34d2ad236f794e30865757cec4a7776087d48d5b4f8
- Cap holder
- 0x0000…0002Address0x0000000000000000000000000000000000000000000000000000000000000002LabelNone known
- Source
- Not verified
- Storage deposit
- 0.01045 SUI
- Publish tx
- 672ymm…rk3f
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) 0x468b…5d5c, 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 | 0x468b…5d5c | 0x32f2…e3ceAddress0x32f205839784554db3ae9fcafecb26c6cdbd4903b4033b2407d5647b9e63e3ceLabelNone known | 672ymm…rk3f | … |
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 | 15 | |
| Sui Framework | 0x0000…0002 | Same | 33 |