Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x871c9246923301e9feef033608b75419ce065dc3180e5e2c9f2ae4635c3d3cadKindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xf270…ce9c
- 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
- 0x2b10…e584Object0x2b101d3a5971ec6645aabad7ec37e50744ab05bfb60a7ea6b77716d2ae33e584
- Cap holder
- Scam packageScam package0x871c9246923301e9feef033608b75419ce065dc3180e5e2c9f2ae4635c3d3cadKindScamSourcetide registry
- Source
- Not verified
- Storage deposit
- 0.0093252 SUI
- Publish tx
- Auqzp1…4Jg6
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| SuiReward | 1 | 1 | 1 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xf270…ce9c, 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 | 0xf270…ce9c | Scam deployerScam deployer0x871c9246923301e9feef033608b75419ce065dc3180e5e2c9f2ae4635c3d3cadKindDeployerSourceHeuristic, medium confidence | Auqzp1…4Jg6 | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 9 | |
| Sui Framework | 0x0000…0002 | Same | 27 |