Package 0xc4c3…40a1
Package0xc4c3…40a1
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x53fe…4378Address0x53fe7feee6baed4fd8b3e759d425df9182ca0712a3858a8e617714245fbb4378LabelNone known
- Package ID
- 0xc4c3…40a1
- 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
- 0xa66f…17b7Object0xa66f00d162d4479d1b8e2495f61f5be0cc207b182702f1fb056c3ff0034817b7
- Cap holder
- 0x53fe…4378Address0x53fe7feee6baed4fd8b3e759d425df9182ca0712a3858a8e617714245fbb4378LabelNone known
- Source
- Not verified
- Storage deposit
- 0.011248 SUI
- Publish tx
- 3BBwnJ…Q5hS
Modules
3 functions, 2 public, 2 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xc4c3…40a1, 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 | 0xc4c3…40a1 | 0x53fe…4378Address0x53fe7feee6baed4fd8b3e759d425df9182ca0712a3858a8e617714245fbb4378LabelNone known | 3BBwnJ…Q5hS | … |
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 | 20 | |
| Sui Framework | 0x0000…0002 | Same | 47 |