Package 0xfc7e…810a
Package0xfc7e…810a
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- Dungeon Move deployerDungeon Move deployer0x22e9b1da7128eda1e705cea41789e9b1550f70cde2c9134f6bb7cf10a47734f8KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xfc7e…810a
- 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
- 0x3d83…2399Object0x3d83319b903e16b7bbe949741113c63a534ec3a409b0d14e0203c993708f2399
- Cap holder
- Dungeon Move deployerDungeon Move deployer0x22e9b1da7128eda1e705cea41789e9b1550f70cde2c9134f6bb7cf10a47734f8KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.25574 SUI
- Publish tx
- Cm4etZ…6PK8
Modules
1 functions, 1 public, 0 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xfc7e…810a, 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 | 0xfc7e…810a | Dungeon Move deployerDungeon Move deployer0x22e9b1da7128eda1e705cea41789e9b1550f70cde2c9134f6bb7cf10a47734f8KindDeployerSourceHeuristic, medium confidence | Cm4etZ…6PK8 | … |
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 | 8 | |
| Sui Framework | 0x0000…0002 | Same | 25 |