Package 0x4d2e…3cb0
Package0x4d2e…3cb0
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xac0a…ccc4Address0xac0a0df85b3b3c6fc1d6aca18a3782a170f9a23f9f6552088b9a7142d1eeccc4LabelNone known
- Package ID
- 0x4d2e…3cb0
- 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
- 0x6a44…cd1dObject0x6a447cd8ccdd9171a51deaeb8236b0d57c7a03354d2e29144d48f61c849acd1d
- Cap holder
- 0xac0a…ccc4Address0xac0a0df85b3b3c6fc1d6aca18a3782a170f9a23f9f6552088b9a7142d1eeccc4LabelNone known
- Source
- Not verified
- Storage deposit
- 0.007562 SUI
- Publish tx
- CTCBNQ…fWBh
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) 0x4d2e…3cb0, 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 | 0x4d2e…3cb0 | 0xac0a…ccc4Address0xac0a0df85b3b3c6fc1d6aca18a3782a170f9a23f9f6552088b9a7142d1eeccc4LabelNone known | CTCBNQ…fWBh | … |
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 | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |