|
|
@@ -101,9 +101,9 @@ $ make build
|
|
|
- WORMHOLE_STATE_ID: [0xaeab97f96cf9877fee2883315d459552b2b921edc16d7ceac6eab944dd88919c](https://explorer.sui.io/object/0xaeab97f96cf9877fee2883315d459552b2b921edc16d7ceac6eab944dd88919c)
|
|
|
|
|
|
## 5. Common Questions on How to Integrate with Pyth
|
|
|
-1. What is up with the "sui rev"? (09b2081498366df936abae26eea4b2d5cafb2788). Why does it point to a specific commit hash instead of Sui github "main" or "devnet"?
|
|
|
+1. What is up with the "sui rev"? (`09b2081498366df936abae26eea4b2d5cafb2788`). Why does it point to a specific commit hash instead of Sui github "main" or "devnet"?
|
|
|
|
|
|
-Our Pyth `Move.toml` file looks like the following. It depends on specific versions of the Sui Framework as well as Wormhole. To make your contracts compatible, you must also specify the following dependencies verbatim in your `Move.toml` file. We are locked in to this specific rev because our package depends on Wormhole, which uses this rev.
|
|
|
+Our Pyth `Move.toml` file looks like the following. It depends on specific versions of the Sui Framework as well as Wormhole. To make your contracts compatible, you must also specify the following dependencies verbatim in your `Move.toml` file. We are locked in to this specific `rev` because our package depends on Wormhole, which uses this rev.
|
|
|
```
|
|
|
[dependencies.Sui]
|
|
|
git = "https://github.com/MystenLabs/sui.git"
|
optke3