Scam package
Package0x44eb…4dcc
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0xcfe77d1cde2eb0c69dc07c872d3e131b1fbb59c3f34f1f2cfddbc6cb77296d80KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x44eb…4dcc
- 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
- 0xc561…7612Object0xc5618f240ff1222bf5e426db2e779ec274e9903e5e2b60cbf7ddc36e5a897612
- Cap holder
- Scam deployerScam deployer0xcfe77d1cde2eb0c69dc07c872d3e131b1fbb59c3f34f1f2cfddbc6cb77296d80KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.031274 SUI
- Publish tx
- nT7c4q…QVkg
Modules
15 functions, 10 public, 5 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x44eb…4dcc, 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 | 0x44eb…4dcc | Scam deployerScam deployer0xcfe77d1cde2eb0c69dc07c872d3e131b1fbb59c3f34f1f2cfddbc6cb77296d80KindDeployerSourceHeuristic, medium confidence | nT7c4q…QVkg | … |
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 | 8 | |
| Sui Framework | 0x0000…0002 | Same | 26 |