Package 0x0c1a…0df3
Package0x0c1a…0df3
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xdf8a…14d9Address0xdf8a629f014d257041ecb00cc28152f9033fa41a90c014f22ec3bb6ae0b014d9LabelNone known
- Package ID
- 0x0c1a…0df3
- 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
- 0x3e28…47d5Object0x3e280fdbb8b619c9e068a476f96781b3694b67dd1458a6b52a5a57e5c15447d5
- Cap holder
- 0xdf8a…14d9Address0xdf8a629f014d257041ecb00cc28152f9033fa41a90c014f22ec3bb6ae0b014d9LabelNone known
- Source
- Not verified
- Storage deposit
- 0.186276 SUI
- Publish tx
- 33ym2P…Z7Gt
Modules
1 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| hollydog | 0 | 0 | 1 | 7 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x0c1a…0df3, 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 | 0x0c1a…0df3 | 0xdf8a…14d9Address0xdf8a629f014d257041ecb00cc28152f9033fa41a90c014f22ec3bb6ae0b014d9LabelNone known | 33ym2P…Z7Gt | … |
Recent calls
No calls to this package found
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 |