YouSUI package
Package0x3cba…9f84
Package details
- Project
- YouSUIProtocol
- Version
- 1 of 1
- Publisher
- YouSUI deployerYouSUI deployer0x9df04aa401743eb0b1552edc09f6194ea271955300ca4f0054c7f7b42067680eKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x3cba…9f84
- 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
- 0x08fd…d12fObject0x08fdd452e9ac639e1c16ca0107cc71227866056a2621abf8aadcb07cb23ad12f
- Cap holder
- YouSUI deployerYouSUI deployer0x9df04aa401743eb0b1552edc09f6194ea271955300ca4f0054c7f7b42067680eKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0114608 SUI
- Publish tx
- 2Ko9Fc…pRr4
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) 0x3cba…9f84, 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 | 0x3cba…9f84 | YouSUI deployerYouSUI deployer0x9df04aa401743eb0b1552edc09f6194ea271955300ca4f0054c7f7b42067680eKindDeployerSourceHeuristic, medium confidence | 2Ko9Fc…pRr4 | … |
Recent calls
No calls to this package found
Dependencies
The exact versions this package was linked against
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 1 | |
| Sui Framework | 0x0000…0002 | Same | 5 |