Capo package
Package0x6b42…504e
Package details
- Project
- CapoProject
- Version
- 1 of 1
- Publisher
- Capo deployerCapo deployer0x2cf44b3d69b90d63ebcb4200cf08dcdee79c33b4febacf0bfcdcb8915a630385KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x6b42…504e
- 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
- 0x4303…279eObject0x43035c9c74511bbffce5c0317437092b392aeb8d7e34919764fd5161c162279e
- Cap holder
- Capo deployerCapo deployer0x2cf44b3d69b90d63ebcb4200cf08dcdee79c33b4febacf0bfcdcb8915a630385KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0087248 SUI
- Publish tx
- 9AEBrE…7LBe
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) 0x6b42…504e, 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 | 0x6b42…504e | Capo deployerCapo deployer0x2cf44b3d69b90d63ebcb4200cf08dcdee79c33b4febacf0bfcdcb8915a630385KindDeployerSourceHeuristic, medium confidence | 9AEBrE…7LBe | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |