1000XSUI package
Package0x9f3f…7e69
Package details
- Project
- 1000XSUIProject
- Version
- 1 of 1
- Publisher
- 1000XSUI deployer1000XSUI deployer0x0b3ed2cf74d7f8387542581f91a0bf802440e832a31ddb54ac8e0c38e1eb0033KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x9f3f…7e69
- 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
- 0x6dc3…0f03Object0x6dc33e08464ff085ee6dc1ff64053c9b7704088e129fa30c2c44367496130f03
- Cap holder
- 1000XSUI deployer1000XSUI deployer0x0b3ed2cf74d7f8387542581f91a0bf802440e832a31ddb54ac8e0c38e1eb0033KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0072884 SUI
- Publish tx
- 2VfikQ…WoNU
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) 0x9f3f…7e69, 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 | 0x9f3f…7e69 | 1000XSUI deployer1000XSUI deployer0x0b3ed2cf74d7f8387542581f91a0bf802440e832a31ddb54ac8e0c38e1eb0033KindDeployerSourceHeuristic, medium confidence | 2VfikQ…WoNU | … |
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 | 16 | |
| Sui Framework | 0x0000…0002 | Same | 34 |