Scam package
Package0x4509…11bd
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x447f3b601d514c3e7be2b21d657d238008996045f67fae2e904335e3791e1b55KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x4509…11bd
- 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
- 0xeeaf…4b90Object0xeeaf6363a6de0c659c718698f3f17a7d49bc057f79110d7dfbf176c8759e4b90
- Cap holder
- Scam deployerScam deployer0x447f3b601d514c3e7be2b21d657d238008996045f67fae2e904335e3791e1b55KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.009424 SUI
- Publish tx
- FCuEbH…r94t
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) 0x4509…11bd, 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 | 0x4509…11bd | Scam deployerScam deployer0x447f3b601d514c3e7be2b21d657d238008996045f67fae2e904335e3791e1b55KindDeployerSourceHeuristic, medium confidence | FCuEbH…r94t | … |
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 |