Package 0x2011…f4cc
Package0x2011…f4cc
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x66f1…4c2cAddress0x66f145c85cb4926ca3db093b00c649485439126cb1439fd470ceb48c83224c2cLabelNone known
- Package ID
- 0x2011…f4cc
- 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
- 0x6f86…d891Object0x6f8618aa8b6e319b9127125956b1ca43a808aa805b21703d347a0a91f5bdd891
- Cap holder
- 0x66f1…4c2cAddress0x66f145c85cb4926ca3db093b00c649485439126cb1439fd470ceb48c83224c2cLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0564756 SUI
- Publish tx
- HQLDhA…rczB
Modules
1 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| suirrito | 0 | 0 | 1 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x2011…f4cc, 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 | 0x2011…f4cc | 0x66f1…4c2cAddress0x66f145c85cb4926ca3db093b00c649485439126cb1439fd470ceb48c83224c2cLabelNone known | HQLDhA…rczB | … |
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 |