You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/smart_contract_sdk/my_first_contract.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Download the smart contract examples respository at [https://github.com/parallel
25
25
26
26
After this folder is downloaded, enter into `my_first_contract` directory.
27
27
28
-
Build `my_first_contract` contract using `pchain_compile`. Please refer to ["Building and Deploying the Contract"](build_deploy_contract.md) session for detailed steps. The build process will generate an optimized Web Assembly (WASM) binary on your current path if no destination path is provided to the CLI
28
+
Build `my_first_contract` contract using `pchain_compile`. Please refer to ["Building and Deploying the Contract"](build_contract.md) session for detailed steps. The build process will generate an optimized Web Assembly (WASM) binary on your current path if no destination path is provided to the CLI
29
29
by the name of <PACKAGE_NAME>.wasm where `PACKAGE_NAME` refers to the package name specified on your Cargo manifest. The user is free to use any other toolchain like Cargo as well to build the smart contract
30
30
but for verification of the contract deployment through the ["Contract Publishing Service"](../getting_started/contract_publish.md), the use of `pchain_compile` is highly recommended.
31
31
@@ -49,8 +49,8 @@ but for verification of the contract deployment through the ["Contract Publishin
49
49
</details>
50
50
51
51
52
-
See ["Building and Deploying the Contract"](/smart_contract_sdk/build_deploy_contract)
53
-
on how to achieve this. However, please note that the `optimize_tool` may lead to breaking changes in more complex code. Future updates in `testnet1` will focus on handling these issues.
52
+
See ["Building and Deploying the Contract"](build_contract.md)
53
+
on how to achieve this. However, please note that the `optimize_tool` may lead to breaking changes in more complex code. Future updates in `testnet2` will focus on handling these issues.
0 commit comments