Scam package
Package0x34e7…49b1
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x95e769761cd196a7db03c0fc0eada5a97a576b8bbd677b00bde1615285b0efb3KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x34e7…49b1
- 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
- 0x3c31…23b7Object0x3c3159c49960dc733973ea207139ea86b339aa687064c5420a8dc0b9d69e23b7
- Cap holder
- Scam deployerScam deployer0x95e769761cd196a7db03c0fc0eada5a97a576b8bbd677b00bde1615285b0efb3KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.00874 SUI
- Publish tx
- 4DCpJ2…ypCp
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) 0x34e7…49b1, 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 | 0x34e7…49b1 | Scam deployerScam deployer0x95e769761cd196a7db03c0fc0eada5a97a576b8bbd677b00bde1615285b0efb3KindDeployerSourceHeuristic, medium confidence | 4DCpJ2…ypCp | … |
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 |