Scam package
Package0xfd5c…62ce
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0xd303f8e493de9eedcc98e847410155e2c45a8895761b181c350792a8b8b2c0c9KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xfd5c…62ce
- 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
- 0xee5d…a218Object0xee5d3b6f8e8b0c524de4b4f05cd000dcaf0a7e0d39287b3d852b4d276a22a218
- Cap holder
- Scam deployerScam deployer0xd303f8e493de9eedcc98e847410155e2c45a8895761b181c350792a8b8b2c0c9KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.008208 SUI
- Publish tx
- HUoB1D…Pz5u
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) 0xfd5c…62ce, 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 | 0xfd5c…62ce | Scam deployerScam deployer0xd303f8e493de9eedcc98e847410155e2c45a8895761b181c350792a8b8b2c0c9KindDeployerSourceHeuristic, medium confidence | HUoB1D…Pz5u | … |
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 | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |