DRIFE package
Package0x294d…af0e
Package details
- Project
- DRIFEProject
- Version
- 1 of 1
- Publisher
- DRIFE deployerDRIFE deployer0xe09b48ffe84dd2770658af3d9494927e398fea220b5abb3335eddd851bf129b2KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x294d…af0e
- 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
- 0x580b…adefObject0x580bba721f9d63975ca3df500e7267a9266fe92d1e6c18619bf838ec540cadef
- Cap holder
- DRIFE deployerDRIFE deployer0x7a0ffc176e12f1c1bd6b38eed1b3fef20740a4667455286124cfb60a2244eb6dKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0160892 SUI
- Publish tx
- AmUK1p…Ca3c
Modules
4 functions, 2 public, 6 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x294d…af0e, 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 | 0x294d…af0e | DRIFE deployerDRIFE deployer0xe09b48ffe84dd2770658af3d9494927e398fea220b5abb3335eddd851bf129b2KindDeployerSourceHeuristic, medium confidence | AmUK1p…Ca3c | … |
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 | 8 | |
| Sui Framework | 0x0000…0002 | Same | 25 |