Pupui package
Package0xb95c…b091
Package details
- Project
- PupuiProject
- Version
- 1 of 1
- Publisher
- Pupui deployerPupui deployer0x06bd3a8733c2bcf0639df80cdb3182c7df9f46063eb8aadf4c7472a8a839db8cKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xb95c…b091
- 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
- 0x9323…2d4fObject0x9323614eb667d0c2cf214aaec0247ee393ba5529d8cbad1a2793a39079db2d4f
- Cap holder
- Pupui deployerPupui deployer0x06bd3a8733c2bcf0639df80cdb3182c7df9f46063eb8aadf4c7472a8a839db8cKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.007448 SUI
- Publish tx
- Husp2y…6rq5
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) 0xb95c…b091, 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 | 0xb95c…b091 | Pupui deployerPupui deployer0x06bd3a8733c2bcf0639df80cdb3182c7df9f46063eb8aadf4c7472a8a839db8cKindDeployerSourceHeuristic, medium confidence | Husp2y…6rq5 | … |
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 |