Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x48410dc2c4db448f8ec4b9e2d60a81b632c4b4492636a0fc58086865430ef4e0KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x8bbf…fc2c
- 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
- 0x8c82…e4b2Object0x8c82263336400df1e140ecce472c2f57e9a84b474a9a41a41d18a61828c1e4b2
- Cap holder
- Scam deployerScam deployer0x48410dc2c4db448f8ec4b9e2d60a81b632c4b4492636a0fc58086865430ef4e0KindScamSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0135128 SUI
- Publish tx
- BCfjaB…adXY
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| nft_claim | 6 | 1 | 3 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x8bbf…fc2c, 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 | 0x8bbf…fc2c | Scam deployerScam deployer0x48410dc2c4db448f8ec4b9e2d60a81b632c4b4492636a0fc58086865430ef4e0KindDeployerSourceHeuristic, medium confidence | BCfjaB…adXY | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |