/
Search by name, SuiNS, address, digest, object ID, coin type or checkpoint.
Search by name, SuiNS, address, digest, object ID, coin type or checkpoint.
Package details
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.
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x980c…3145, 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 | 0x980c…3145 | NODO deployerNODO deployer0x943850f207a7d71d7473cf3781dc34f822b12cd130a71a04b72f5e6d00008663KindDeployerSourceHeuristic, medium confidence | 2XtWm6…YVb2 | … |
Reading recent calls
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 16 | |
| Sui Framework | 0x0000…0002 | Same | 36 |