NAVI package
Package details
- Project
- NAVILending
- Version
- 1 of 1
- Publisher
- NAVI deployerNAVI deployer0xe179806bd80f973ccd37d324a50a9ba48c6aeb7adb596e8d906a9189974efe7eKindDeployerProjectNAVISourceHeuristic, medium confidence
- Package ID
- 0xa99b…44b5
- 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
- 0x82f2…f836Object0x82f2e779467d7abb47c4f685eb6fdddc68ee5f4e2052f0bc3631378264c2f836
- Cap holder
- NAVI oracle updater senderNAVI oracle updater sender0x39c70d4ce3ce769a46f46ad80184a88bc25be9b49545751f5425796ef0c3d9baKindProtocolProjectNAVISourcetide registry, medium confidence
- Source
- Not verified
- Storage deposit
- 0.00741 SUI
- Publish tx
- Dnewyg…tg6f
Modules
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xa99b…44b5, 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 | 0xa99b…44b5 | NAVI deployerNAVI deployer0xe179806bd80f973ccd37d324a50a9ba48c6aeb7adb596e8d906a9189974efe7eKindDeployerProjectNAVISourceHeuristic, medium confidence | Dnewyg…tg6f | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 3 | |
| Sui Framework | 0x0000…0002 | Same | 16 |