Package 0x0c8a…4dc3
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- CetusCetus0x0c7b2650e2f9e996c22cb8ae8c529f2abf1463c99f22a3b51a1c0d5e4cce5acaKindProtocolProjectCetusSourcetide registry
- Package ID
- 0x0c8a…4dc3
- 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
- 0xf0b5…7341Object0xf0b5420e82e56dce24946d82fb36ecdc053d305e6dcba739dc5381a9d7287341
- Cap holder
- 0x4a70…d329Address0x4a7039cdc3007cdb5d5f269151d0a8acf22def54197aba2060d325ea9502d329LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0095076 SUI
- Publish tx
- DJGFsd…K2vf
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| lp_token | 0 | 0 | 2 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x0c8a…4dc3, 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 | 0x0c8a…4dc3 | CetusCetus0x0c7b2650e2f9e996c22cb8ae8c529f2abf1463c99f22a3b51a1c0d5e4cce5acaKindProtocolProjectCetusSourcetide registry | DJGFsd…K2vf | … |
Recent calls
No calls to this package found
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 5 | |
| Sui Framework | 0x0000…0002 | Same | 20 |