Package 0x20b2…c353
Package0x20b2…c353
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x9546…0ba7Address0x95463db0ca7dfe2db1c5bb911be6c5a67e49f27b842ec2f0c0ca2b2a36ce0ba7LabelNone known
- Package ID
- 0x20b2…c353
- 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
- 0xd695…fbc2Object0xd695f17abfbb864ac5c1dfa80e23e72e7df982e1234b4f2743e3260d8239fbc2
- Cap holder
- 0x9546…0ba7Address0x95463db0ca7dfe2db1c5bb911be6c5a67e49f27b842ec2f0c0ca2b2a36ce0ba7LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0090744 SUI
- Publish tx
- 7pXq7C…PehL
Modules
2 functions, 1 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x20b2…c353, 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 | 0x20b2…c353 | 0x9546…0ba7Address0x95463db0ca7dfe2db1c5bb911be6c5a67e49f27b842ec2f0c0ca2b2a36ce0ba7LabelNone known | 7pXq7C…PehL | … |
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 | 15 | |
| Sui Framework | 0x0000…0002 | Same | 33 |