Package 0x0d4a…79d1
Package0x0d4a…79d1
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xa936…ddb5Address0xa9366380361d862bde6e5d2b66d0ed513a6c107dc7c2cdd9fd1c34471577ddb5LabelNone known
- Package ID
- 0x0d4a…79d1
- 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
- 0xaca9…7d82Object0xaca9be655f7f90da44ba438c2d619c2d688aad39624561724c5b5c4e5e1e7d82
- Cap holder
- 0xa936…ddb5Address0xa9366380361d862bde6e5d2b66d0ed513a6c107dc7c2cdd9fd1c34471577ddb5LabelNone known
- Source
- Not verified
- Storage deposit
- 0.1047204 SUI
- Publish tx
- GaW4Ma…2e14
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) 0x0d4a…79d1, 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 | 0x0d4a…79d1 | 0xa936…ddb5Address0xa9366380361d862bde6e5d2b66d0ed513a6c107dc7c2cdd9fd1c34471577ddb5LabelNone known | GaW4Ma…2e14 | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |