Package 0x1483…8fcd
Package0x1483…8fcd
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x27a8…cb74Address0x27a83db11e0bd60a97da92f5ef5ae812324db217ee666ee8e212ca325e16cb74LabelNone known
- Package ID
- 0x1483…8fcd
- 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
- 0x1448…41c0Object0x1448d0370a52cfcc7bcab80d7a0a176e3b1ad417277f20a0c8a5a6871f7641c0
- Cap holder
- 0x27a8…cb74Address0x27a83db11e0bd60a97da92f5ef5ae812324db217ee666ee8e212ca325e16cb74LabelNone known
- Source
- Not verified
- Storage deposit
- 0.009918 SUI
- Publish tx
- 4oTHiY…gEpP
Modules
2 functions, 1 public, 2 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| fishdick | 1 | 0 | 2 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x1483…8fcd, 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 | 0x1483…8fcd | 0x27a8…cb74Address0x27a83db11e0bd60a97da92f5ef5ae812324db217ee666ee8e212ca325e16cb74LabelNone known | 4oTHiY…gEpP | … |
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 | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |