Package 0xbbbc…2cfd
Package0xbbbc…2cfd
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xe569…f0a1Address0xe5690a5ca130a6955c021a5416450ce6f69eef0cf8e95d55b16599989147f0a1LabelNone known
- Package ID
- 0xbbbc…2cfd
- 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
- 0xe0f3…a02dObject0xe0f37e010e9377e1dd2445c1f12835908d0ae490df3ccbe561a92f89c041a02d
- Cap holder
- 0x0000…0002Address0x0000000000000000000000000000000000000000000000000000000000000002LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0074252 SUI
- Publish tx
- 332yvz…jVFv
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) 0xbbbc…2cfd, 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 | 0xbbbc…2cfd | 0xe569…f0a1Address0xe5690a5ca130a6955c021a5416450ce6f69eef0cf8e95d55b16599989147f0a1LabelNone known | 332yvz…jVFv | … |
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 | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |