Package 0xaaa3…b3f2
Package0xaaa3…b3f2
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x2fa9…d586Address0x2fa9a182c1f87a2d77cefd9f9f93e53abd71988bf2750b6cce9f9f6ef306d586LabelNone known
- Package ID
- 0xaaa3…b3f2
- 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
- 0xe141…a631Object0xe1411ef67cb386ff93102613d0e3427ea15f9028656e99cd03b3857e7dcaa631
- Cap holder
- 0x2fa9…d586Address0x2fa9a182c1f87a2d77cefd9f9f93e53abd71988bf2750b6cce9f9f6ef306d586LabelNone known
- Source
- Not verified
- Storage deposit
- 0.140296 SUI
- Publish tx
- EH3xwJ…Ujmh
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) 0xaaa3…b3f2, 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 | 0xaaa3…b3f2 | 0x2fa9…d586Address0x2fa9a182c1f87a2d77cefd9f9f93e53abd71988bf2750b6cce9f9f6ef306d586LabelNone known | EH3xwJ…Ujmh | … |
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 |