Package 0x15e8…e4dd
Package0x15e8…e4dd
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x05fb…d980Address0x05fbb17bf7b68f40c4948fc4aaef762b2569ab5d9424c403f7282d7e9339d980LabelNone known
- Package ID
- 0x15e8…e4dd
- 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
- 0xbb1c…a4c9Object0xbb1c8e76f95eb8e8d2506eb55df18c367732ec914cbc8f7c5c7c9239eb9ea4c9
- Cap holder
- 0x05fb…d980Address0x05fbb17bf7b68f40c4948fc4aaef762b2569ab5d9424c403f7282d7e9339d980LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0080788 SUI
- Publish tx
- 7U8EUF…XZdJ
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) 0x15e8…e4dd, 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 | 0x15e8…e4dd | 0x05fb…d980Address0x05fbb17bf7b68f40c4948fc4aaef762b2569ab5d9424c403f7282d7e9339d980LabelNone known | 7U8EUF…XZdJ | … |
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 | 13 | |
| Sui Framework | 0x0000…0002 | Same | 30 |