Package 0xa099…1cd2
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xd7f8…bde5Address0xd7f8cd5a669772bc555f9efdb1d02c273f350c3b8d89788576e0e7a26e74bde5LabelNone known
- Package ID
- 0xa099…1cd2
- 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
- 0x8381…cdbbObject0x83818e58dfeec5db0fceed633254fec3b392a380f9156bdd2bcdfb546116cdbb
- Cap holder
- 0xd7f8…bde5Address0xd7f8cd5a669772bc555f9efdb1d02c273f350c3b8d89788576e0e7a26e74bde5LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0425372 SUI
- Publish tx
- 2xdArh…N5JK
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| my_minter | 5 | 5 | 7 | 24 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xa099…1cd2, 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 | 0xa099…1cd2 | 0xd7f8…bde5Address0xd7f8cd5a669772bc555f9efdb1d02c273f350c3b8d89788576e0e7a26e74bde5LabelNone known | 2xdArh…N5JK | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 | |
| minter (0xaa2a…f9eb) | 0xc1f9…43d8 | 0xaa2a…f9eb | 5 |