Package 0x818e…d2c7
Package0x818e…d2c7
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x8095…c3aeAddress0x80958e18bb6f4f6259ff1943de9925fda7a1a937703c1e3c6eaf5670c50cc3aeLabelNone known
- Package ID
- 0x818e…d2c7
- 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
- 0x7ef8…b6edObject0x7ef8950a3ab0caacfa1c4f1a90b3769ed3f953c88083643ca75ebacb89a9b6ed
- Cap holder
- 0x8095…c3aeAddress0x80958e18bb6f4f6259ff1943de9925fda7a1a937703c1e3c6eaf5670c50cc3aeLabelNone known
- Source
- Not verified
- Storage deposit
- 0.00836 SUI
- Publish tx
- 7mBbFn…M5cF
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) 0x818e…d2c7, 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 | 0x818e…d2c7 | 0x8095…c3aeAddress0x80958e18bb6f4f6259ff1943de9925fda7a1a937703c1e3c6eaf5670c50cc3aeLabelNone known | 7mBbFn…M5cF | … |
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 |