Galxe package
Package details
- Project
- GalxeProject
- Version
- 1 of 1
- Publisher
- Galxe deployerGalxe deployer0xc930b7433a70e3007a86506d70f05217fbadd10702dcd96cb0ec21896ee67451KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x5d98…e92e
- 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
- 0x9ae1…4eeaObject0x9ae196ccee4ffe1dbd12346c31dc0604dbff11ed39b637885069c35b834f4eea
- Cap holder
- Galxe deployerGalxe deployer0xc930b7433a70e3007a86506d70f05217fbadd10702dcd96cb0ec21896ee67451KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0164616 SUI
- Publish tx
- AvjkyK…7QuM
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| deliver | 2 | 2 | 6 | 10 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x5d98…e92e, 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 | 0x5d98…e92e | Galxe deployerGalxe deployer0xc930b7433a70e3007a86506d70f05217fbadd10702dcd96cb0ec21896ee67451KindDeployerSourceHeuristic, medium confidence | AvjkyK…7QuM | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |