Package 0xff70…41ea
Package0xff70…41ea
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x105c…bd53Address0x105c780dda6f87c2ec32d5c7127f34d5c80bb559116fc294d8fd8f7395c2bd53LabelNone known
- Package ID
- 0xff70…41ea
- 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
- 0xd005…8913Object0xd005293dc289ba6148f4f97298848ae1cfae3aba113975da028278596d248913
- Cap holder
- 0x105c…bd53Address0x105c780dda6f87c2ec32d5c7127f34d5c80bb559116fc294d8fd8f7395c2bd53LabelNone known
- Source
- Not verified
- Storage deposit
- 0.1220864 SUI
- Publish tx
- 251Def…hrKh
Modules
1 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| suicide | 0 | 0 | 1 | 7 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xff70…41ea, 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 | 0xff70…41ea | 0x105c…bd53Address0x105c780dda6f87c2ec32d5c7127f34d5c80bb559116fc294d8fd8f7395c2bd53LabelNone known | 251Def…hrKh | … |
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 |