Scam package
Package0x0c5e…84d3
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x7dec8d1749d249d7ab72befdc8a7dc08dfd6ea8d636f04d8f2336d57c60a2587KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x0c5e…84d3
- 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
- 0x2408…afbdObject0x2408170417e8c5e45a1166217d814e9e216431b201e51ca97be40d64030eafbd
- Cap holder
- Scam deployerScam deployer0x7dec8d1749d249d7ab72befdc8a7dc08dfd6ea8d636f04d8f2336d57c60a2587KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.008246 SUI
- Publish tx
- 57rqp3…NU9q
Modules
1 functions, 0 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x0c5e…84d3, 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 | 0x0c5e…84d3 | Scam deployerScam deployer0x7dec8d1749d249d7ab72befdc8a7dc08dfd6ea8d636f04d8f2336d57c60a2587KindDeployerSourceHeuristic, medium confidence | 57rqp3…NU9q | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |