Package 0xf228…ca77
Package0xf228…ca77
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0xadae…59a3Address0xadae0d6550ce94cc4ebea2af5e3e161b8e66145bd88872bb82c817057e6259a3LabelNone known
- Package ID
- 0xf228…ca77
- 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
- 0x120c…11b0Object0x120c79ea541e958ec8b5cfc7bce22422153f34948a0faf2c559277d6a9cd11b0
- Cap holder
- 0xadae…59a3Address0xadae0d6550ce94cc4ebea2af5e3e161b8e66145bd88872bb82c817057e6259a3LabelNone known
- Source
- Not verified
- Storage deposit
- 0.0103056 SUI
- Publish tx
- 9bvesd…dagx
Modules
4 functions, 3 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| bearcoin | 3 | 3 | 1 | 3 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xf228…ca77, 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 | 0xf228…ca77 | 0xadae…59a3Address0xadae0d6550ce94cc4ebea2af5e3e161b8e66145bd88872bb82c817057e6259a3LabelNone known | 9bvesd…dagx | … |
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 | 1 | |
| Sui Framework | 0x0000…0002 | Same | 5 |