Attention package
Package0x0ef3…7522
Package details
- Project
- AttentionProject
- Version
- 1 of 1
- Publisher
- Attention deployerAttention deployer0x0fa70c486ae1779e8014b7c445bbdbc99ca182592a52f75e69e77207d76c2b29KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0x0ef3…7522
- 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
- 0x5f38…11fcObject0x5f389e50ccc3be6ef9169fbe494839397dc5a3e71d49a1404905fa0f379211fc
- Cap holder
- Attention deployerAttention deployer0x0fa70c486ae1779e8014b7c445bbdbc99ca182592a52f75e69e77207d76c2b29KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.2941048 SUI
- Publish tx
- E4uoxH…jApa
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) 0x0ef3…7522, 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 | 0x0ef3…7522 | Attention deployerAttention deployer0x0fa70c486ae1779e8014b7c445bbdbc99ca182592a52f75e69e77207d76c2b29KindDeployerSourceHeuristic, medium confidence | E4uoxH…jApa | … |
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 | 16 | |
| Sui Framework | 0x0000…0002 | Same | 34 |