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.
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| bridge_sui | 12 | 11 | 8 | 9 | ||
| smove | 0 | 0 | 1 | 4 |
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xd9f9…de7f, 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 | 0xd9f9…de7f | BlueMove deployerBlueMove deployer0x7d823d7c8cd081bd9c4cbb02d92f36fa2bacbf3f5a7fb44ac4886b2abd14e035KindDeployerProjectBlueMoveSourceHeuristic, medium confidence | 8UZrYf…NG2Z | … |
Reading recent calls
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 1 | |
| Sui Framework | 0x0000…0002 | Same | 4 |