Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x83d833e50ac052378f950edaf3b39168735d09d9202f8311b42940cef2d91950KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x44e9…b262
- 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
- 0xe138…206bObject0xe1389c5e8105c6ac24e1b7024a02f85e3540442929cedda710bbc1c6bc28206b
- Cap holder
- Scam deployerScam deployer0x83d833e50ac052378f950edaf3b39168735d09d9202f8311b42940cef2d91950KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0146072 SUI
- Publish tx
- ApFaoo…EQk1
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| navxgift5606 | 2 | 2 | 4 | 12 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x44e9…b262, 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 | 0x44e9…b262 | Scam deployerScam deployer0x83d833e50ac052378f950edaf3b39168735d09d9202f8311b42940cef2d91950KindDeployerSourceHeuristic, medium confidence | ApFaoo…EQk1 | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 8 | |
| Sui Framework | 0x0000…0002 | Same | 25 |