Scam package
Package0x60b7…c804
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x64d5dd64c6c04cf90ff251ab6fa749dee391dfd95e5a3c4d6b578971eb62ed0cKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x60b7…c804
- 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
- 0xf3b1…945bObject0xf3b16eb79aa41b66dd02c1d48bf96015f2cb541b0e9be477eb74a5d5db1f945b
- Cap holder
- Scam deployerScam deployer0x64d5dd64c6c04cf90ff251ab6fa749dee391dfd95e5a3c4d6b578971eb62ed0cKindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0093252 SUI
- Publish tx
- 4e5nWs…YE22
Modules
2 functions, 1 public, 2 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x60b7…c804, 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 | 0x60b7…c804 | Scam deployerScam deployer0x64d5dd64c6c04cf90ff251ab6fa749dee391dfd95e5a3c4d6b578971eb62ed0cKindDeployerSourceHeuristic, medium confidence | 4e5nWs…YE22 | … |
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 | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |