Package 0x97e2…05cf
Package0x97e2…05cf
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xc0e7…fadeAddress0xc0e733794de3078406aeacb327a8d55aa58fb433246e9d90f94a7f4dccfafadeLabelNone known
- Package ID
- 0x97e2…05cf
- 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
- 0x61e7…63c9Object0x61e7d528a915bd8390fd04754b839c2ac1871161c991025425c8ac6e7b8163c9
- Cap holder
- 0xc0e7…fadeAddress0xc0e733794de3078406aeacb327a8d55aa58fb433246e9d90f94a7f4dccfafadeLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0080256 SUI
- Publish tx
- A87T29…vpCh
Modules
2 functions, 1 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| swavo_points | 1 | 0 | 1 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x97e2…05cf, 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 | 0x97e2…05cf | 0xc0e7…fadeAddress0xc0e733794de3078406aeacb327a8d55aa58fb433246e9d90f94a7f4dccfafadeLabelNone known | A87T29…vpCh | … |
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 | 16 | |
| Sui Framework | 0x0000…0002 | Same | 37 |