Package 0xec85…5c19
Package0xec85…5c19
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xd99d…21d5Address0xd99d7d774f3ed72a88dd721cae683821f13b8c6a0021cfbd3f31113c6adb21d5LabelNone known
- Package ID
- 0xec85…5c19
- 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
- 0xb851…efa5Object0xb851a1e1dc420b77163af8c632c46abb0d6e7f9e4aabebc836eaf2d29c54efa5
- Cap holder
- 0xd99d…21d5Address0xd99d7d774f3ed72a88dd721cae683821f13b8c6a0021cfbd3f31113c6adb21d5LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0371716 SUI
- Publish tx
- ENB44R…eHWc
Modules
17 functions, 7 public, 5 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xec85…5c19, 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 | 0xec85…5c19 | 0xd99d…21d5Address0xd99d7d774f3ed72a88dd721cae683821f13b8c6a0021cfbd3f31113c6adb21d5LabelNone known | ENB44R…eHWc | … |
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 | 14 | |
| Sui Framework | 0x0000…0002 | Same | 30 | |
| curve (0x50a3…c918) | 0x50a3…c918 | Same | 1 |