Package 0x313d…d2d2
Package0x313d…d2d2
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x840b…4ef6Address0x840b8bc04506846993b22cd916ff6552e88992e7baa974c5a8384227baed4ef6LabelNone known
- Package ID
- 0x313d…d2d2
- 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
- 0xb6c5…4397Object0xb6c514805dcf70a33743579c2828af1fb8c104d9d2fdee155a900a0220ee4397
- Cap holder
- 0x2005…1c96Address0x2005ac8f847d6e917c151dc62180c2463801ec79714ea971ebaa6a5d24c51c96LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0102372 SUI
- Publish tx
- nvpzsv…9Drq
Modules
2 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| FARTCOIN | 0 | 1 | 1 | 4 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x313d…d2d2, 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 | 0x313d…d2d2 | 0x840b…4ef6Address0x840b8bc04506846993b22cd916ff6552e88992e7baa974c5a8384227baed4ef6LabelNone known | nvpzsv…9Drq | … |
Recent calls
Reading recent calls
Dependencies
The exact versions this package was linked against
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 10 | |
| Sui Framework | 0x0000…0002 | Same | 28 |