Package 0x01ec…1199

Package0x01ec…1199

Not the latest version. This is version 2 of 4. Open the latest

Package details

Project: Not labelled
Version: 2 of 4
Publisher: 0xd1db…1caa
Package ID: 0x01ec…1199
Original ID: 0x1f46…0d8b
Published: 2 years ago
Upgraded: a year ago
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: 0x96bb…aa1c
Cap holder: 0xd1db…1caa
Source: Not verified
Storage deposit: 0.0752172 SUI
Publish tx: 7WTBC4…umtJ
Upgrade tx: HhpnRd…jn7c

Modules

33 functions, 4 public, 14 structs

Module	Public functions	Entry functions	Structs	Constants	Friend modules
launchpad	4	12	12	7
mint_box	0	0	1	3	launchpad
pseudorandom	0	0	1	2	launchpad mint_box
signature	0	0	0	1	launchpad

Upgrade history

Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x1f46…0d8b, and the version number counts up, so the highest number is the current code, version 4 here.

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 4Latest	0x81a7…df57	a year ago	0xd1db…1caa	4B2gJ3…S6dN	…
Version 3	0x8555…b857	a year ago	0xd1db…1caa	983G2g…vafk	…
Version 2Viewing	0x01ec…1199	a year ago	0xd1db…1caa	HhpnRd…jn7c	…
Version 1Published, original ID	0x1f46…0d8b	2 years ago	0xd1db…1caa	7WTBC4…umtJ	…

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	34
@mysten/kiosk	0xdfb4…e5f3	0x434b…7879	4