Package 0x25c9…c9ca
Package0x25c9…c9ca
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x24a6…e933Address0x24a683317636b59e83c408e1e1a72456e512e3a5be819e279a8bfa2138b7e933LabelNone known
- Package ID
- 0x25c9…c9ca
- 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
- 0xa828…8d66Object0xa828d9bb699ee17ed3f31b97abe8dcb989161c3bf81af76e6bfccfa868048d66
- Cap holder
- 0x24a6…e933Address0x24a683317636b59e83c408e1e1a72456e512e3a5be819e279a8bfa2138b7e933LabelNone known
- Source
- Not verified
- Storage deposit
- 0.1778704 SUI
- Publish tx
- 725N6q…zcY1
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) 0x25c9…c9ca, 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 | 0x25c9…c9ca | 0x24a6…e933Address0x24a683317636b59e83c408e1e1a72456e512e3a5be819e279a8bfa2138b7e933LabelNone known | 725N6q…zcY1 | … |
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 | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |