Jackson package
Package0x5ffe…2dad
Package details
- Project
- JacksonProject
- Version
- 1 of 1
- Publisher
- Jackson deployerJackson deployer0xb8a606d9a14a25e66322ec8e86c0e45cdf55645c298d9d4f0a4c5749c9a8b32bKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x5ffe…2dad
- 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
- 0xc90b…4105Object0xc90bdaeedef7ccbc720d6f3de95f471b521c9bec22081e4391363ae878094105
- Cap holder
- Jackson deployerJackson deployer0xb8a606d9a14a25e66322ec8e86c0e45cdf55645c298d9d4f0a4c5749c9a8b32bKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.008626 SUI
- Publish tx
- F762PY…FpqA
Modules
1 functions, 1 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x5ffe…2dad, 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 | 0x5ffe…2dad | Jackson deployerJackson deployer0xb8a606d9a14a25e66322ec8e86c0e45cdf55645c298d9d4f0a4c5749c9a8b32bKindDeployerSourceHeuristic, medium confidence | F762PY…FpqA | … |
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 | 19 | |
| Sui Framework | 0x0000…0002 | Same | 45 |