Package 0x787c…46c7
Package0x787c…46c7
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- BayswapBayswap0xaf6b4ee9ccf7aa203f7df0983e3e1fbe98741acf17822ff2a28de91e0a1dc59bKindProtocolSourcetide registry
- Package ID
- 0x787c…46c7
- 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
- 0x0725…dc7dObject0x0725022906fcecd9142f89ed46802ebd37634816a64ecec0a6238ffedd79dc7d
- Cap holder
- BayswapBayswap0xaf6b4ee9ccf7aa203f7df0983e3e1fbe98741acf17822ff2a28de91e0a1dc59bKindProtocolSourcetide registry
- Source
- Not verified
- Storage deposit
- 0.0236056 SUI
- Publish tx
- 2SxaB5…vkCt
Modules
8 functions, 5 public, 5 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x787c…46c7, 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 | 0x787c…46c7 | BayswapBayswap0xaf6b4ee9ccf7aa203f7df0983e3e1fbe98741acf17822ff2a28de91e0a1dc59bKindProtocolSourcetide registry | 2SxaB5…vkCt | … |
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 | 1 | |
| Sui Framework | 0x0000…0002 | Same | 5 |