Haedal package
Package0x1571…1105
Package details
- Project
- HaedalLiquid staking and vaults
- Version
- 1 of 1
- Publisher
- Haedal deployerHaedal deployer0x5cfbfd965a03883f92127ab43330c0b9527a949b93dd4d34b0c3012793fa807dKindDeployerProjectHaedalSourceHeuristic, medium confidence
- Package ID
- 0x1571…1105
- 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
- 0xd1f9…a172Object0xd1f9de7e4b584d35f69d272a4510946cc8a19405adfdf2d251094d952969a172
- Cap holder
- HaedalHaedal0x5cfbfd965a03883f92127ab43330c0b9527a949b93dd4d34b0c3012793fa807dKindProtocolProjectHaedalSourcetide registry
- Source
- Not verified
- Storage deposit
- 0.0074252 SUI
- Publish tx
- GtpbUv…Lsj8
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) 0x1571…1105, 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 | 0x1571…1105 | Haedal deployerHaedal deployer0x5cfbfd965a03883f92127ab43330c0b9527a949b93dd4d34b0c3012793fa807dKindDeployerProjectHaedalSourceHeuristic, medium confidence | GtpbUv…Lsj8 | … |
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 |