Package 0xa495…3d58
Package0xa495…3d58
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x875e…8406Address0x875ef3dbde04975bbf1eb36b9325dfd937f74a855cd1b3de2d595b92f3c98406LabelNone known
- Package ID
- 0xa495…3d58
- 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
- 0x1010…6c41Object0x10105c373756f857cfdd4a3f657a4f12cb7f4eac0842a9f1df401a354a406c41
- Cap holder
- 0x875e…8406Address0x875ef3dbde04975bbf1eb36b9325dfd937f74a855cd1b3de2d595b92f3c98406LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0118636 SUI
- Publish tx
- BVdN4W…vc7V
Modules
7 functions, 5 public, 4 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| dispatcher | 5 | 3 | 4 | 0 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xa495…3d58, 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 | 0xa495…3d58 | 0x875e…8406Address0x875ef3dbde04975bbf1eb36b9325dfd937f74a855cd1b3de2d595b92f3c98406LabelNone known | BVdN4W…vc7V | … |
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 | 16 | |
| Sui Framework | 0x0000…0002 | Same | 35 |