Package 0x6aa0…0b33
Package0x6aa0…0b33
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x2177…ee65Address0x2177b7aef39dc9c5143f98cf73ac45a9254e600ee6f262574c4b9305593dee65LabelNone known
- Package ID
- 0x6aa0…0b33
- 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
- 0xd265…0579Object0xd26598387a4e36ac7bb8860fd9750043464418051cc971a6a6052c34622b0579
- Cap holder
- 0x2177…ee65Address0x2177b7aef39dc9c5143f98cf73ac45a9254e600ee6f262574c4b9305593dee65LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0085196 SUI
- Publish tx
- B1aF14…mUcB
Modules
2 functions, 1 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| trollface | 1 | 1 | 1 | 5 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x6aa0…0b33, 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 | 0x6aa0…0b33 | 0x2177…ee65Address0x2177b7aef39dc9c5143f98cf73ac45a9254e600ee6f262574c4b9305593dee65LabelNone known | B1aF14…mUcB | … |
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 | 1 | |
| Sui Framework | 0x0000…0002 | Same | 4 |