RWA package
Package0xc2b2…5a6e
Package details
- Project
- RWAProject
- Version
- 1 of 1
- Publisher
- RWA deployerRWA deployer0xfb296de5eac465796956d1ea6b0af4f53ac7705db44b9d0fb9cc9e857a53b0d2KindDeployerSourceHeuristic, medium confidence
- Package ID
- 0xc2b2…5a6e
- 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
- 0xd6f3…274dObject0xd6f342dbfdf096f93f2f7998d9b1664b4b077814cea65242b747e0dd6f75274d
- Cap holder
- RWA deployerRWA deployer0xfb296de5eac465796956d1ea6b0af4f53ac7705db44b9d0fb9cc9e857a53b0d2KindDeployerSourceHeuristic, medium confidence
- Source
- Not verified
- Storage deposit
- 0.133 SUI
- Publish tx
- ENpNZs…ZKZZ
Modules
1 functions, 0 public, 1 structs
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0xc2b2…5a6e, 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 | 0xc2b2…5a6e | RWA deployerRWA deployer0xfb296de5eac465796956d1ea6b0af4f53ac7705db44b9d0fb9cc9e857a53b0d2KindDeployerSourceHeuristic, medium confidence | ENpNZs…ZKZZ | … |
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 | 18 | |
| Sui Framework | 0x0000…0002 | Same | 40 |