unicorn SUI package
Package0x49d0…cd30
Package details
- Project
- unicorn SUIProject
- Version
- 1 of 1
- Publisher
- unicorn SUI deployerunicorn SUI deployer0x325d0920d722a827130e0fb1c8a944dc40fcf9bec5fe35c2f5d535aab5b55c11KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x49d0…cd30
- 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
- 0x6239…93d7Object0x62391507e7149ebeddf5a42601df5f2fc394abc0d9169105e7c8bd0b347a93d7
- Cap holder
- unicorn SUI deployerunicorn SUI deployer0x325d0920d722a827130e0fb1c8a944dc40fcf9bec5fe35c2f5d535aab5b55c11KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.2438688 SUI
- Publish tx
- J9iGra…WYmM
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) 0x49d0…cd30, 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 | 0x49d0…cd30 | unicorn SUI deployerunicorn SUI deployer0x325d0920d722a827130e0fb1c8a944dc40fcf9bec5fe35c2f5d535aab5b55c11KindDeployerSourceHeuristic, medium confidence | J9iGra…WYmM | … |
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 | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |