Package 0x29c2…c84e
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x7d69…2d0aAddress0x7d69319ade58b9dc92fd921cc9b538430e3e32c7933e92968d971d3afae32d0aLabelNone known
- Package ID
- 0x29c2…c84e
- 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
- 0xc17a…3b5cObject0xc17af5cc658b111983efc7f2406226fbd6d925edb7e34ca08b866918cc8f3b5c
- Cap holder
- 0x7d69…2d0aAddress0x7d69319ade58b9dc92fd921cc9b538430e3e32c7933e92968d971d3afae32d0aLabelNone known
- Source
- Not verified
- Storage deposit
- 0.1442252 SUI
- Publish tx
- Hvb5G9…Yq2p
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| collection | 67 | 25 | 30 | 62 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x29c2…c84e, 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 | 0x29c2…c84e | 0x7d69…2d0aAddress0x7d69319ade58b9dc92fd921cc9b538430e3e32c7933e92968d971d3afae32d0aLabelNone known | Hvb5G9…Yq2p | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 25 | |
| Sui Framework | 0x0000…0002 | Same | 59 | |
| @mysten/kiosk | 0xdfb4…e5f3 | 0x434b…7879 | 4 |