Package 0xa095…6adf
Package0xa095…6adf
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xeac9…c27dAddress0xeac945be384a56dec67535d90ddfa479f5338a762cc6a14592ce3ee3cfe7c27dLabelNone known
- Package ID
- 0xa095…6adf
- 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
- 0x11c5…65bfObject0x11c5909580fa5d5706a98c144d12ffa870fb21a4eece65d5ba33b067512e65bf
- Cap holder
- 0xeac9…c27dAddress0xeac945be384a56dec67535d90ddfa479f5338a762cc6a14592ce3ee3cfe7c27dLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0083524 SUI
- Publish tx
- BmjTK5…uzHK
Modules
1 functions, 0 public, 2 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| nft5486 | 0 | 0 | 2 | 5 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xa095…6adf, 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 | 0xa095…6adf | 0xeac9…c27dAddress0xeac945be384a56dec67535d90ddfa479f5338a762cc6a14592ce3ee3cfe7c27dLabelNone known | BmjTK5…uzHK | … |
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 | 13 | |
| Sui Framework | 0x0000…0002 | Same | 30 |