Package 0x2fce…5bbd
Package0x2fce…5bbd
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xd5c2…c183Address0xd5c21472312ceb9d8b2ee93b3896217e4a23e9b83379beef14f1f3e1543ac183LabelNone known
- Package ID
- 0x2fce…5bbd
- 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
- 0xbf53…6e3bObject0xbf538e28c9074f95dc17bfc0f57ddef256e50f5f173df2c6c4c7836a828f6e3b
- Cap holder
- 0xd5c2…c183Address0xd5c21472312ceb9d8b2ee93b3896217e4a23e9b83379beef14f1f3e1543ac183LabelNone known
- Source
- Not verified
- Storage deposit
- 0.007106 SUI
- Publish tx
- 6dwPhe…NTQr
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) 0x2fce…5bbd, 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 | 0x2fce…5bbd | 0xd5c2…c183Address0xd5c21472312ceb9d8b2ee93b3896217e4a23e9b83379beef14f1f3e1543ac183LabelNone known | 6dwPhe…NTQr | … |
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 | 16 | |
| Sui Framework | 0x0000…0002 | Same | 37 |