Package 0x28ab…f910
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- Full Sail deployerFull Sail deployer0x8c30bf5bfd2fb00bd9198599ea1bf6ae84f3b1855a238ed458765dd2adce0340KindDeployerProjectFull SailSourceHeuristic, medium confidence
- Package ID
- 0x28ab…f910
- 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
- 0x3a9e…e3f5Object0x3a9ea134b7f328d0f022bc1d986e3014e9e8ca326692ed686a83641fc608e3f5
- Cap holder
- Full Sail deployerFull Sail deployer0x8c30bf5bfd2fb00bd9198599ea1bf6ae84f3b1855a238ed458765dd2adce0340KindDeployerProjectFull SailSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0070528 SUI
- Publish tx
- 8Jn5vM…bb5g
Modules
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x28ab…f910, 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 | 0x28ab…f910 | Full Sail deployerFull Sail deployer0x8c30bf5bfd2fb00bd9198599ea1bf6ae84f3b1855a238ed458765dd2adce0340KindDeployerProjectFull SailSourceHeuristic, medium confidence | 8Jn5vM…bb5g | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 16 | |
| Sui Framework | 0x0000…0002 | Same | 37 |