diff --git a/docs/faq/faq.md b/docs/faq/faq.md index 2ec10fca5f..c475cd1037 100644 --- a/docs/faq/faq.md +++ b/docs/faq/faq.md @@ -131,7 +131,7 @@ you compile a contract in `--release` mode. 1. __Set the log level of your node to `runtime::contracts=debug`.__
For example, to have only errors and debug output show up for the `canvas-node`: ``` - canvas --dev --tmp -lerror,runtime::contracts=debug + substrate-contracts-node --dev --tmp -lerror,runtime::contracts=debug ``` __Important: Debug output is only printed for RPC calls or off-chain tests ‒ not for transactions!__ diff --git a/docs/getting-started/compiling.md b/docs/getting-started/compiling.md index bf42ecd781..084a13230c 100644 --- a/docs/getting-started/compiling.md +++ b/docs/getting-started/compiling.md @@ -52,5 +52,5 @@ If you look closely at the constructors and messages, you will also notice a `se contains a 4-byte hash of the function name and is used to route your contract calls to the correct functions. -In the next section we will start a [Substrate Canvas node](https://github.com/paritytech/canvas-node) +In the next section we will start a [Substrate Smart Contracts node](https://github.com/paritytech/canvas-node) and configure the [Canvas UI](https://github.com/paritytech/canvas-ui) to interact with it. \ No newline at end of file diff --git a/docs/getting-started/deploying.md b/docs/getting-started/deploying.md index c1e06116c7..86496a25af 100644 --- a/docs/getting-started/deploying.md +++ b/docs/getting-started/deploying.md @@ -3,7 +3,7 @@ title: Deploy Your Contract slug: /getting-started/deploy-your-contract --- -Now that we have generated the Wasm binary from our source code and started a Canvas node, we want to deploy this contract onto our Substrate blockchain. +Now that we have generated the Wasm binary from our source code and started a Substrate Smart Contracts node, we want to deploy this contract onto our blockchain. Smart contract deployment on Substrate is a little different than on traditional smart contract blockchains. diff --git a/docs/getting-started/running.md b/docs/getting-started/running.md index 35f396db23..3b146394a2 100644 --- a/docs/getting-started/running.md +++ b/docs/getting-started/running.md @@ -11,7 +11,7 @@ It's a comfortable option if you want to get a quickstart. [After successfully installing `canvas`](/getting-started/setup), you can start a local development chain by running: ```bash -canvas --dev --tmp +substrate-contracts-node --dev --tmp ``` ![An image of the terminal starting a Substrate node](./assets/start-substrate-node.png) diff --git a/docs/getting-started/setup.md b/docs/getting-started/setup.md index dcdd38f17d..4de1d63b71 100644 --- a/docs/getting-started/setup.md +++ b/docs/getting-started/setup.md @@ -45,14 +45,14 @@ rustup component add rust-src --toolchain nightly rustup target add wasm32-unknown-unknown --toolchain nightly ``` -## Installing The Canvas Node +## Installing The Substrate Smart Contracts Node -The [canvas-node](https://github.com/paritytech/canvas-node#note) is a simple Substrate +The [substrate-contracts-node](https://github.com/paritytech/substrate-contracts-node) is a simple Substrate blockchain which is configured to include the Substrate module for smart contract functionality ‒ the `contracts` pallet (see [How it Works](/how-it-works) for more). It's a comfortable option if you want to get a quickstart. ```bash -cargo install canvas-node --git https://github.com/paritytech/canvas-node.git --tag v0.1.9 --force --locked +cargo install contracts-node --git https://github.com/paritytech/substrate-contracts-node.git --tag v0.1.0 --force --locked ``` diff --git a/docs/getting-started/troubleshooting.md b/docs/getting-started/troubleshooting.md index ce086b9793..494a2fddaf 100644 --- a/docs/getting-started/troubleshooting.md +++ b/docs/getting-started/troubleshooting.md @@ -13,14 +13,14 @@ There is a known issue with the Substrate block production (BABE) on a running c ClientImport("Unexpected epoch change") ``` -To solve this you will need to restart your node with: `canvas --dev --tmp`. At that point, you will +To solve this you will need to restart your node with: `substrate-contracts-node --dev --tmp`. At that point, you will need to re-deploy any contracts and re-do any steps that you may have done before on your node. As long as you keep your node running, you should face no issues. ### Old Contracts in Local Storage **Canvas UI** uses its own local storage to track the contracts that you have deployed. This means -that if you deploy a contract using the UI, and then purge your Canvas node, you will be prompted to +that if you deploy a contract using the UI, and then purge your Substrate node, you will be prompted to reset your local storage and please do so. And then re-deploy any contracts and re-do any steps that you may have done before on your node.