Scam package
Package0x047b…9f98
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0xf111a7bb1eaf203bd921ef62f1d232c06dd9ce91b91f0cd386c55356566a8dceKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x047b…9f98
- 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
- 0xab16…59cdObject0xab16692eeb8409795c97a4eb0870e06e93ae1ab87defe18f39a38b3d69e059cd
- Cap holder
- Scam deployerScam deployer0xf111a7bb1eaf203bd921ef62f1d232c06dd9ce91b91f0cd386c55356566a8dceKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0086564 SUI
- Publish tx
- BzM86Q…2Bnm
Modules
2 functions, 1 public, 2 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x047b…9f98, 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 | 0x047b…9f98 | Scam deployerScam deployer0xf111a7bb1eaf203bd921ef62f1d232c06dd9ce91b91f0cd386c55356566a8dceKindDeployerSourceHeuristic, medium confidence | BzM86Q…2Bnm | … |
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 | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |