Package 0x307e…50af
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- Scam deployerScam deployer0x7e257c51b3d8eeb1ea92b0f4f5650bcddf77de5a858002a9115feb34d1f0a33dKindScamSourceHeuristic, medium confidence
- Package ID
- 0x307e…50af
- 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
- 0x42e1…67e7Object0x42e19645528f42fb20176cf0af2e825fa857105bf2aaf62e329deef4302667e7
- Cap holder
- Scam deployerScam deployer0x7e257c51b3d8eeb1ea92b0f4f5650bcddf77de5a858002a9115feb34d1f0a33dKindScamSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.0102676 SUI
- Publish tx
- 71Tbpn…aq75
Modules
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| NSAirdrop | 1 | 1 | 2 | 10 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x307e…50af, 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 | 0x307e…50af | Scam deployerScam deployer0x7e257c51b3d8eeb1ea92b0f4f5650bcddf77de5a858002a9115feb34d1f0a33dKindScamSourceHeuristic, medium confidence | 71Tbpn…aq75 | … |
Recent calls
Reading recent calls
Dependencies
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 11 | |
| Sui Framework | 0x0000…0002 | Same | 28 |