feat: add IOTA testnet

Author: trungtt198x

pages/price-feeds/use-real-time-data/iota.mdx

@@ -106,7 +106,8 @@ const priceIDs = [
 
 const priceUpdateData = await connection.getPriceFeedsUpdateData(priceIDs);
 
-// It is either injected from the browser or instantiated in the backend via some private key
+// It is either injected from the browser (https://www.npmjs.com/package/@iota/dapp-kit)
+// or instantiated in the backend via some private key (https://www.npmjs.com/package/@iota/iota-sdk)
 const wallet: SignerWithProvider = getWallet();
 // Get the state IDs of the Pyth and Wormhole contracts from
 // https://docs.pyth.network/price-feeds/contract-addresses/iota
@@ -126,14 +127,15 @@ tx.moveCall({
 });
 
 const txBlock = {
-    transactionBlock: tx,
+    transaction: tx,
+    wallet,
     options: {
         showEffects: true,
         showEvents: true,
     },
 };
 
-const result = await wallet.signAndExecuteTransactionBlock(txBlock);
+const result = await wallet.signAndExecuteTransaction(txBlock);
 ```
 
 By calling the `updatePriceFeeds` function, the `IotaPythClient` adds the necessary transactions to the transaction block to update the price feeds.
@@ -142,9 +144,9 @@ By calling the `updatePriceFeeds` function, the `IotaPythClient` adds the necess
 
 Your IOTA Move module **should NOT** have a hard-coded call to `pyth::update_single_price_feed.` In other words, a contract should **never call** the IOTA Pyth `pyth::update_single_price_feed` entry point. Instead, it should be called directly from client code (e.g., Typescript or Rust).
 
-When IOTA contracts are [upgraded](<(https://docs.IOTA.io/build/package-upgrades)>), the address changes, which makes the old address no longer valid. If your module has a hard-coded call to `pyth::update_single_price_feed` living at a fixed call-site, it may eventually get bricked due to how Pyth upgrades are implemented. (Pyth only allow users to interact with the most recent package version for security reasons).
+When IOTA contracts are [upgraded](https://docs.iota.org/developer/iota-101/move-overview/package-upgrades/introduction), the address changes, which makes the old address no longer valid. If your module has a hard-coded call to `pyth::update_single_price_feed` living at a fixed call-site, it may eventually get bricked due to how Pyth upgrades are implemented. (Pyth only allow users to interact with the most recent package version for security reasons).
 
-Therefore, you should build a [IOTA programmable transaction](https://docs.IOTA.io/build/prog-trans-ts-sdk) that first updates the price by calling `pyth::update_single_price_feed` at the latest call-site from the client-side and then call a function in your contract that invokes `pyth::get_price` on the `PriceInfoObject` to get the recently updated price.
+Therefore, you should build a [IOTA programmable transaction](https://docs.iota.org/developer/iota-101/transactions/ptb/programmable-transaction-blocks-overview) that first updates the price by calling `pyth::update_single_price_feed` at the latest call-site from the client-side and then call a function in your contract that invokes `pyth::get_price` on the `PriceInfoObject` to get the recently updated price.
 You can use `IOTAPythClient` to build such transactions and handle all the complexity of updating the price feeds.
 
 Consult [Fetch Price Updates](../fetch-price-updates) for more information on how to fetch the `pyth_price_update`.
@@ -168,7 +170,7 @@ You can run this example with `npm run example-relay`. A full command that updat
 export IOTA_KEY=YOUR_PRIV_KEY;
 npm run example-relay -- --feed-id "5a035d5440f5c163069af66062bac6c79377bf88396fa27e6067bfca8096d280" \
 --hermes "https://hermes-beta.pyth.network" \
---full-node "https://fullnode.testnet.IOTA.io:443" \
+--full-node "https://api.testnet.iota.cafe" \
 --pyth-state-id "0xd3e79c2c083b934e78b3bd58a490ec6b092561954da6e7322e1e2b3c8abfddc0" \
 --wormhole-state-id "0x31358d198147da50db32eda2562951d53973a0c0ad5ed738e9b17d88b213d790"
 ```