Package 0x91c6…04c8
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x0c78…a932Address0x0c788a1f0bfcae2282b6357f2e66b98377971fd743cd651160b4ac5be07da932LabelNone known
- Package ID
- 0x91c6…04c8
- 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
- 0x7d49…fcdaObject0x7d49f745425272558b1b17ae0a4164c97b68ba482d1aa312b8e936cdcb71fcda
- Cap holder
- 0x0c78…a932Address0x0c788a1f0bfcae2282b6357f2e66b98377971fd743cd651160b4ac5be07da932LabelNone known
- Source
- Not verified
- Storage deposit
- 0.014402 SUI
- Publish tx
- BJavca…3qK4
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| accc | 6 | 0 | 1 | 2 | ||
| version_control | 2 | 0 | 2 | 3 | accc |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x91c6…04c8, 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 | 0x91c6…04c8 | 0x0c78…a932Address0x0c788a1f0bfcae2282b6357f2e66b98377971fd743cd651160b4ac5be07da932LabelNone known | BJavca…3qK4 | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 19 | |
| Sui Framework | 0x0000…0002 | Same | 45 |