Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x606e6799fa440994f78a4cd9a5cb8391720198d9ba5d85316579b7183df6afbcKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xc1f5…e5e2
- 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
- 0xbee0…70b5Object0xbee05a80e0b63eb0fab41f0bfc79b4801e0a0becb1a4243939f36658f7a870b5
- Cap holder
- Scam deployerScam deployer0x606e6799fa440994f78a4cd9a5cb8391720198d9ba5d85316579b7183df6afbcKindScamSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0128896 SUI
- Publish tx
- 8siVus…sXFJ
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| reward9663 | 1 | 0 | 3 | 12 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xc1f5…e5e2, 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 | 0xc1f5…e5e2 | Scam deployerScam deployer0x606e6799fa440994f78a4cd9a5cb8391720198d9ba5d85316579b7183df6afbcKindDeployerSourceHeuristic, medium confidence | 8siVus…sXFJ | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |