Scam package
Package0x0c64…9cfd
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x7871dab6f485c523366352004e6af875bd4262ed9792c06a7e5a808441b31e5fKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x0c64…9cfd
- 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
- 0xea42…5d74Object0xea425e3333a58b1cc470e428ad2f93084438e7b0b0f1158ad706ba9ca8ad5d74
- Cap holder
- Scam deployerScam deployer0x7871dab6f485c523366352004e6af875bd4262ed9792c06a7e5a808441b31e5fKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0086564 SUI
- Publish tx
- 9y7jjn…sM4D
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) 0x0c64…9cfd, 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 | 0x0c64…9cfd | Scam deployerScam deployer0x7871dab6f485c523366352004e6af875bd4262ed9792c06a7e5a808441b31e5fKindDeployerSourceHeuristic, medium confidence | 9y7jjn…sM4D | … |
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 |