Package 0x8e0e…967f
Package0x8e0e…967f
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x2f4e…fea8Address0x2f4e147884751c6a4a5722f4a0048074b60aaf7adad4a6388a4a7d10f26afea8LabelNone known
- Package ID
- 0x8e0e…967f
- 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
- 0xb645…b494Object0xb6452ebc1458c830aa0db0c1eae74afef0f13bf84e2a46d37bd3c6c34ae8b494
- Cap holder
- 0x2f4e…fea8Address0x2f4e147884751c6a4a5722f4a0048074b60aaf7adad4a6388a4a7d10f26afea8LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0068324 SUI
- Publish tx
- 6Gn53D…ED7S
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) 0x8e0e…967f, 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 | 0x8e0e…967f | 0x2f4e…fea8Address0x2f4e147884751c6a4a5722f4a0048074b60aaf7adad4a6388a4a7d10f26afea8LabelNone known | 6Gn53D…ED7S | … |
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 | 25 | |
| Sui Framework | 0x0000…0002 | Same | 60 |