Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x54f373ac85ba61f725105b6934795f6940a3f49fcb3d60501a58bef20356b4d5KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xd64f…4c84
- 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
- 0xac2d…d26bObject0xac2d7564f4b70f6175b65bb26b039d9b43c664eaa029971d6893b899b7ccd26b
- Cap holder
- Scam deployerScam deployer0x54f373ac85ba61f725105b6934795f6940a3f49fcb3d60501a58bef20356b4d5KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0096596 SUI
- Publish tx
- G7ECHY…sW5W
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| movexnft9174 | 1 | 0 | 2 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xd64f…4c84, 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 | 0xd64f…4c84 | Scam deployerScam deployer0x54f373ac85ba61f725105b6934795f6940a3f49fcb3d60501a58bef20356b4d5KindDeployerSourceHeuristic, medium confidence | G7ECHY…sW5W | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |