Scam package
Package0xb4cb…62b5
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x242220bd1af015f90c994f9e1e8bb6c66dbddb37c2044010dd2cd92b5d6809b9KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xb4cb…62b5
- 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
- 0x2844…d0f0Object0x2844994472eb8f1602eecca98e8695db7cb435d14992ba948d9e85924d02d0f0
- Cap holder
- Scam deployerScam deployer0x242220bd1af015f90c994f9e1e8bb6c66dbddb37c2044010dd2cd92b5d6809b9KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0081776 SUI
- Publish tx
- As7jdX…LTWj
Modules
1 functions, 0 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xb4cb…62b5, 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 | 0xb4cb…62b5 | Scam deployerScam deployer0x242220bd1af015f90c994f9e1e8bb6c66dbddb37c2044010dd2cd92b5d6809b9KindDeployerSourceHeuristic, medium confidence | As7jdX…LTWj | … |
Recent calls
No calls to this package found
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 |