SeaFi package
Package0xb779…1cca
Package details
- Project
- SeaFiProtocol
- Version
- 1 of 1
- Publisher
- SeaFi deployerSeaFi deployer0x0dd0106a909560b8f2e0262e9946008e307ae7758fde5277853088d25b0b6c7fKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xb779…1cca
- 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
- 0x42e7…4043Object0x42e771873e73dba766c25f73c28baa0345c17a129e3fdd5614741b1134604043
- Cap holder
- SeaFi deployerSeaFi deployer0x0dd0106a909560b8f2e0262e9946008e307ae7758fde5277853088d25b0b6c7fKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.010222 SUI
- Publish tx
- E9ufct…x33j
Modules
2 functions, 1 public, 2 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xb779…1cca, 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 | 0xb779…1cca | SeaFi deployerSeaFi deployer0x0dd0106a909560b8f2e0262e9946008e307ae7758fde5277853088d25b0b6c7fKindDeployerSourceHeuristic, medium confidence | E9ufct…x33j | … |
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 | 2 | |
| Sui Framework | 0x0000…0002 | Same | 9 |