Package 0x0a4e…d8f2
Package0x0a4e…d8f2
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x99cd…091fAddress0x99cdaa6b01f9db90ac2df22e32820adbb3b6d093554f4f20f952f97fe01c091fLabelNone known
- Package ID
- 0x0a4e…d8f2
- 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
- 0xf3af…8d8dObject0xf3af0432d963b3c3ba66e9e80bf496ba9b29b13909c2fdcff0afc8ff89158d8d
- Cap holder
- 0x99cd…091fAddress0x99cdaa6b01f9db90ac2df22e32820adbb3b6d093554f4f20f952f97fe01c091fLabelNone known
- Source
- Not verified
- Storage deposit
- 0.0080788 SUI
- Publish tx
- DJB8ct…CAMH
Modules
1 functions, 0 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x0a4e…d8f2, 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 | 0x0a4e…d8f2 | 0x99cd…091fAddress0x99cdaa6b01f9db90ac2df22e32820adbb3b6d093554f4f20f952f97fe01c091fLabelNone known | DJB8ct…CAMH | … |
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 | 13 | |
| Sui Framework | 0x0000…0002 | Same | 30 |