Package 0x244a…10e1
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xb79d…2b7eAddress0xb79d26a38d40730a67b89b34b754042e46b7485e394f41faff61f3fdeb8a2b7eLabelNone known
- Package ID
- 0x244a…10e1
- 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
- 0xfd1d…1374Object0xfd1d09eb6e1b9db86f2b75989d1b893ffe03ce08d620c5722d9b1c257a741374
- Cap holder
- 0x0000…0002Address0x0000000000000000000000000000000000000000000000000000000000000002LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0071592 SUI
- Publish tx
- 4XWoTP…HuYN
Modules
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x244a…10e1, 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 | 0x244a…10e1 | 0xb79d…2b7eAddress0xb79d26a38d40730a67b89b34b754042e46b7485e394f41faff61f3fdeb8a2b7eLabelNone known | 4XWoTP…HuYN | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |