Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x4958da61f6d3644d04db7d18036ed05fa7666fe9eef823e5e37bf4e8f24b771dKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xe4da…b411
- 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
- 0xfa95…d6d7Object0xfa9588ce485e6d54b1398f6238745612b3d138798f1155dcc21447b07e7ed6d7
- Cap holder
- Scam deployerScam deployer0x4958da61f6d3644d04db7d18036ed05fa7666fe9eef823e5e37bf4e8f24b771dKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0086412 SUI
- Publish tx
- 4HKuEm…HsFa
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| movexnft8658 | 1 | 0 | 2 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xe4da…b411, 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 | 0xe4da…b411 | Scam deployerScam deployer0x4958da61f6d3644d04db7d18036ed05fa7666fe9eef823e5e37bf4e8f24b771dKindDeployerSourceHeuristic, medium confidence | 4HKuEm…HsFa | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |