Scam package
Package details
- Project
- ScamScam
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x6bd633f3171f543fcf8774fbd2725ccf5dfcb732c80b9d00dac6ea8438e62393KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x1ba7…97a8
- 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
- 0x29bc…4645Object0x29bcf2c610b77ea0712c7ab95bd41e114d7fc25e223c3c2360d7675a04e14645
- Cap holder
- Scam deployerScam deployer0x6bd633f3171f543fcf8774fbd2725ccf5dfcb732c80b9d00dac6ea8438e62393KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0096824 SUI
- Publish tx
- 7vTHTJ…Gqxu
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| movexnft3748 | 1 | 0 | 2 | 6 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x1ba7…97a8, 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 | 0x1ba7…97a8 | Scam deployerScam deployer0x6bd633f3171f543fcf8774fbd2725ccf5dfcb732c80b9d00dac6ea8438e62393KindDeployerSourceHeuristic, medium confidence | 7vTHTJ…Gqxu | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 12 | |
| Sui Framework | 0x0000…0002 | Same | 29 |