PandaSui package
Package0x17a1…a9a6
Package details
- Project
- PandaSuiProject
- Version
- 1 of 1
- Publisher
- PandaSui deployerPandaSui deployer0x9d3032161091172dbdcb7b407d34ecf8e0964637f22946d9257d860c309ceb28KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x17a1…a9a6
- 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
- 0x61f9…b9c4Object0x61f9471f6c849554d227610035eeffa0515d70b9c054def472b048303842b9c4
- Cap holder
- PandaSui deployerPandaSui deployer0x9d3032161091172dbdcb7b407d34ecf8e0964637f22946d9257d860c309ceb28KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0095456 SUI
- Publish tx
- 68etEW…QiDm
Modules
3 functions, 2 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x17a1…a9a6, 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 | 0x17a1…a9a6 | PandaSui deployerPandaSui deployer0x9d3032161091172dbdcb7b407d34ecf8e0964637f22946d9257d860c309ceb28KindDeployerSourceHeuristic, medium confidence | 68etEW…QiDm | … |
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 | 35 |