Package 0x9aa4…6844
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xacf2…9533Address0xacf24bbfb1c7f05b9ddf391dbba24164b0a7b8e2bbaa4e5b2b8795705f879533LabelNone known
- Package ID
- 0x9aa4…6844
- 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
- 0xc98c…f8bfObject0xc98cdba3c7291ed7b14326e6ec4803d3022434f258dcc3ee6357d11666d9f8bf
- Cap holder
- Zero address (burn)Zero address (burn)0x0000000000000000000000000000000000000000000000000000000000000000KindSystem objectSourcetide registry
- Source
- Not verified
- Storage deposit
- 0.010792 SUI
- Publish tx
- 2iPw9C…VS5y
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| member_pass | 5 | 0 | 3 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x9aa4…6844, 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 | 0x9aa4…6844 | 0xacf2…9533Address0xacf24bbfb1c7f05b9ddf391dbba24164b0a7b8e2bbaa4e5b2b8795705f879533LabelNone known | 2iPw9C…VS5y | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 22 | |
| Sui Framework | 0x0000…0002 | Same | 49 |