Package 0x0fc9…d2c2
Package0x0fc9…d2c2
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xa2e5…1a39Address0xa2e5f2b59237a0e2d515b2df99b56d7a11baf8598dfe0d3f396e4ac450801a39LabelNone known
- Package ID
- 0x0fc9…d2c2
- 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
- 0xc4c2…c59eObject0xc4c22147e06c7878f4b04998aa5ab95aa370297d7bdfe4f7064e4884e87cc59e
- Cap holder
- 0xa2e5…1a39Address0xa2e5f2b59237a0e2d515b2df99b56d7a11baf8598dfe0d3f396e4ac450801a39LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0084056 SUI
- Publish tx
- DXBYEL…EvMd
Modules
2 functions, 1 public, 2 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x0fc9…d2c2, 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 | 0x0fc9…d2c2 | 0xa2e5…1a39Address0xa2e5f2b59237a0e2d515b2df99b56d7a11baf8598dfe0d3f396e4ac450801a39LabelNone known | DXBYEL…EvMd | … |
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 | 25 | |
| Sui Framework | 0x0000…0002 | Same | 54 |