Scam package
Package0x43dc…4ee7
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x60db2ae458de2b9cd805f928fc06d3a8265f408bdfd0a0f07ffc7073e7a4b3a8KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x43dc…4ee7
- 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
- 0x9896…5e9bObject0x9896b5ce944860c30b8c483d4be58cf1029b2bb90e3848cc66c24ec542a15e9b
- Cap holder
- Scam deployerScam deployer0x60db2ae458de2b9cd805f928fc06d3a8265f408bdfd0a0f07ffc7073e7a4b3a8KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.008208 SUI
- Publish tx
- 66Pqp2…cQxx
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) 0x43dc…4ee7, 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 | 0x43dc…4ee7 | Scam deployerScam deployer0x60db2ae458de2b9cd805f928fc06d3a8265f408bdfd0a0f07ffc7073e7a4b3a8KindDeployerSourceHeuristic, medium confidence | 66Pqp2…cQxx | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |