Package 0x3d58…bdf7
Package0x3d58…bdf7
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- Bublz deployerBublz deployer0x746e748bd700e4ad7a32ea54f7e2a8cfd29be945bb6ab13ee6c4f34f96fb720cKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x3d58…bdf7
- 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
- 0x2bf2…858dObject0x2bf29b3383faf9ac386c5fa2839bd2738c9d427a4f098df3ac52c2b00c87858d
- Cap holder
- Bublz deployerBublz deployer0x746e748bd700e4ad7a32ea54f7e2a8cfd29be945bb6ab13ee6c4f34f96fb720cKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0086412 SUI
- Publish tx
- 8oZUXx…WEAt
Modules
2 functions, 0 public, 3 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x3d58…bdf7, 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 | 0x3d58…bdf7 | Bublz deployerBublz deployer0x746e748bd700e4ad7a32ea54f7e2a8cfd29be945bb6ab13ee6c4f34f96fb720cKindDeployerSourceHeuristic, medium confidence | 8oZUXx…WEAt | … |
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 | 22 | |
| Sui Framework | 0x0000…0002 | Same | 51 |