Package 0xe372…b1cc
Package0xe372…b1cc
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xcea5…fd6fAddress0xcea5320263358beb6f85c3d1e19fc6f2523b60309443c6251fd74dc3667ffd6fLabelNone known
- Package ID
- 0xe372…b1cc
- 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
- 0xf7f6…f145Object0xf7f646bffa76ad3cc67dd99a3f37fbf9d591b37a8900b6b1d699e29d3095f145
- Cap holder
- 0x0000…0002Address0x0000000000000000000000000000000000000000000000000000000000000002LabelNone known
- Source
- Not verified
- Storage deposit
- 0.007258 SUI
- Publish tx
- 2WY4gn…mN5L
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) 0xe372…b1cc, 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 | 0xe372…b1cc | 0xcea5…fd6fAddress0xcea5320263358beb6f85c3d1e19fc6f2523b60309443c6251fd74dc3667ffd6fLabelNone known | 2WY4gn…mN5L | … |
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 | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |