Package 0xeb9f…8c39
Package0xeb9f…8c39
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xe7ad…2f98Address0xe7ad29433c6c2d8a83fe14f1b70627242c44788936dd54b1b6a33577b7e22f98LabelNone known
- Package ID
- 0xeb9f…8c39
- 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
- 0xf30d…3b3cObject0xf30dbe77e0d1c56a94bbd91826bf2178d39094dd899e28156ad8f979b7d83b3c
- Cap holder
- 0xe7ad…2f98Address0xe7ad29433c6c2d8a83fe14f1b70627242c44788936dd54b1b6a33577b7e22f98LabelNone known
- Source
- Not verified
- Storage deposit
- 0.014022 SUI
- Publish tx
- BSD2DV…X69A
Modules
2 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| chillsui | 0 | 0 | 1 | 5 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xeb9f…8c39, 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 | 0xeb9f…8c39 | 0xe7ad…2f98Address0xe7ad29433c6c2d8a83fe14f1b70627242c44788936dd54b1b6a33577b7e22f98LabelNone known | BSD2DV…X69A | … |
Recent calls
No calls to this package found
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 |