Magikarp package
Package0x467e…1b30
Package details
- Project
- MagikarpProject
- Version
- 1 of 1
- Publisher
- Magikarp deployerMagikarp deployer0x911e19e194d1da00d0bf71dccca48c347c3fe1e2a74a7c5919291f584c5fceb4KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x467e…1b30
- 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
- 0x5be9…d792Object0x5be9159953e870d290c3d8d93f3faad2116066fc723a83256295a17f0928d792
- Cap holder
- Magikarp deployerMagikarp deployer0x911e19e194d1da00d0bf71dccca48c347c3fe1e2a74a7c5919291f584c5fceb4KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0080104 SUI
- Publish tx
- DTAbjF…FPs3
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) 0x467e…1b30, 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 | 0x467e…1b30 | Magikarp deployerMagikarp deployer0x911e19e194d1da00d0bf71dccca48c347c3fe1e2a74a7c5919291f584c5fceb4KindDeployerSourceHeuristic, medium confidence | DTAbjF…FPs3 | … |
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 | 15 | |
| Sui Framework | 0x0000…0002 | Same | 33 |