Cro Protocol package
Package0x0d80…4ef4
Package details
- Project
- Cro ProtocolProtocol
- Version
- 1 of 1
- Publisher
- cro-ag.suicro-ag.sui0xc000c8b75df38f2f435036b446de351c5922a81c7e89a536c349685f617a93f4LabelCro Protocol deployerKindDeployerSourceSuiNS
- Package ID
- 0x0d80…4ef4
- 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
- 0x04ee…8f62Object0x04ee38bd68170bb5a862b00b3103fd333e86a85996e55f9b3f65690b3cc48f62
- Cap holder
- cro-ag.suicro-ag.sui0xc000c8b75df38f2f435036b446de351c5922a81c7e89a536c349685f617a93f4LabelCro Protocol deployerKindDeployerSourceSuiNS
- Source
- Not verified
- Storage deposit
- 0.0081776 SUI
- Publish tx
- CcUWYX…RcMz
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) 0x0d80…4ef4, 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 | 0x0d80…4ef4 | cro-ag.suicro-ag.sui0xc000c8b75df38f2f435036b446de351c5922a81c7e89a536c349685f617a93f4LabelCro Protocol deployerKindDeployerSourceSuiNS | CcUWYX…RcMz | … |
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 | 14 | |
| Sui Framework | 0x0000…0002 | Same | 31 |