Package 0x1a2f…2e6a
Package0x1a2f…2e6a
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xdb25…d336Address0xdb25267051c9c7340309d059e9b9a8e4f311d0a46487f24c61fa0fcfb086d336LabelNone known
- Package ID
- 0x1a2f…2e6a
- 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
- 0x48c7…c341Object0x48c78e3263daf02a5ecddb358517126720935142ec4ad630b0dafd30d6b6c341
- Cap holder
- 0xdb25…d336Address0xdb25267051c9c7340309d059e9b9a8e4f311d0a46487f24c61fa0fcfb086d336LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0806208 SUI
- Publish tx
- Fvxejd…A8hj
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) 0x1a2f…2e6a, 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 | 0x1a2f…2e6a | 0xdb25…d336Address0xdb25267051c9c7340309d059e9b9a8e4f311d0a46487f24c61fa0fcfb086d336LabelNone known | Fvxejd…A8hj | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |