From ff98794b6efcb94dbf3298a649b9409584e7f1d5 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:02:29 -0500 Subject: [PATCH 01/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 3a58edfa..ccd2ad68 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -18,7 +18,7 @@ Before starting the dApp, make sure to have the following prerequisites: - If you’re new to smart contracts, consider learning the basics. Understanding how smart contracts work will enhance your experience with Rootstock development. 2. **Foundry installation using [Foundryup](https://book.getfoundry.sh/getting-started/installation#using-foundryup):** -- This installing information is taken from the official [Foundry documentation](https://book.getfoundry.sh/getting-started/installation#using-foundryup), in case you need to go in detail. +- To install, visit the official [Foundry documentation](https://book.getfoundry.sh/getting-started/installation#using-foundryup), for more information. - Foundryup is the official installer for the Foundry toolchain. You can learn more about it [here](https://github.com/foundry-rs/foundry/blob/master/foundryup/README.md). - If you encounter any issues during installation, refer to the Foundryup [FAQ](https://book.getfoundry.sh/faq.html) for assistance. - Precompiled binaries can be downloaded from the Foundry [GitHub releases page](https://github.com/foundry-rs/foundry/releases). For easier management, we recommend using Foundryup. From 545723658bd59b56931005a68f8785d09eeff76f Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:02:45 -0500 Subject: [PATCH 02/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index ccd2ad68..ea8c2e1c 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -19,7 +19,7 @@ Before starting the dApp, make sure to have the following prerequisites: 2. **Foundry installation using [Foundryup](https://book.getfoundry.sh/getting-started/installation#using-foundryup):** - To install, visit the official [Foundry documentation](https://book.getfoundry.sh/getting-started/installation#using-foundryup), for more information. -- Foundryup is the official installer for the Foundry toolchain. You can learn more about it [here](https://github.com/foundry-rs/foundry/blob/master/foundryup/README.md). +- Foundryup is the official installer for the Foundry toolchain. You can learn more about it in the [Foundryup README](https://github.com/foundry-rs/foundry/blob/master/foundryup/README.md). - If you encounter any issues during installation, refer to the Foundryup [FAQ](https://book.getfoundry.sh/faq.html) for assistance. - Precompiled binaries can be downloaded from the Foundry [GitHub releases page](https://github.com/foundry-rs/foundry/releases). For easier management, we recommend using Foundryup. From 8fd5fcc2f3e4ef58b3cae0cf5aa372d5ead3f5bd Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:03:04 -0500 Subject: [PATCH 03/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index ea8c2e1c..001b8f32 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -27,7 +27,7 @@ To install Foundry in your system, run the following command: ```bash curl -L https://foundry.paradigm.xyz | bash ``` -This will install Foundryup. Simply follow the on-screen instructions, and the ```foundryup``` command will become available in your CLI. +This will install Foundryup. Follow the on-screen instructions, and the `foundryup` command will be available via the CLI. Running ```foundryup``` will automatically install the latest (nightly) versions of the ```precompiled binaries```: ```forge```, ```cast```, ```anvil```, and ```chisel```. For additional options, such as installing a specific version or commit, run ```foundryup --help```. From dfe47f1e15f1fc6280e61207fe661f284f6e3e05 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:04:16 -0500 Subject: [PATCH 04/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 001b8f32..bc997641 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -29,7 +29,7 @@ curl -L https://foundry.paradigm.xyz | bash ``` This will install Foundryup. Follow the on-screen instructions, and the `foundryup` command will be available via the CLI. -Running ```foundryup``` will automatically install the latest (nightly) versions of the ```precompiled binaries```: ```forge```, ```cast```, ```anvil```, and ```chisel```. For additional options, such as installing a specific version or commit, run ```foundryup --help```. +Running `foundryup` automatically installs the latest (nightly) versions of the precompiled binaries: `forge`, `cast`, `anvil`, and `chisel`. For additional options, such as installing a specific version or commit, run `foundryup --help`. **_NOTE: If you’re using Windows, you’ll need to install and use [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) as your terminal, since Foundryup currently doesn’t support Powershell or Command Prompt (Cmd)._** From 8832080d713cfd9d541d058885f6665abde5f5b4 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:04:28 -0500 Subject: [PATCH 05/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index bc997641..ed6d66c0 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -31,7 +31,9 @@ This will install Foundryup. Follow the on-screen instructions, and the `foundry Running `foundryup` automatically installs the latest (nightly) versions of the precompiled binaries: `forge`, `cast`, `anvil`, and `chisel`. For additional options, such as installing a specific version or commit, run `foundryup --help`. -**_NOTE: If you’re using Windows, you’ll need to install and use [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) as your terminal, since Foundryup currently doesn’t support Powershell or Command Prompt (Cmd)._** +:::info[Using Windows] +If you’re using Windows, you’ll need to install and use [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) as your terminal, since Foundryup currently doesn’t support Powershell or Command Prompt (Cmd). +::: 3. **Basic Knowledge of Foundry:** - Familiarity with Foundry's core concepts and functionalities is recommended. If you're new to Foundry, refer to the [Rootstock Foundry Guide](/developers/smart-contracts/foundry/). From b82982e26f9c4ac14f60be926094d86ad8477760 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:05:10 -0500 Subject: [PATCH 06/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index ed6d66c0..aa05bfa7 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -67,7 +67,7 @@ Install all required dependencies using forge: forge install OpenZeppelin/openzeppelin-contracts ``` -### Obtain Rootstock Testnet and Mainnet RPC URLs +### Add Rootstock Testnet and Mainnet RPC URLs This section will walk you through adding Rootstock Testnet and Mainnet RPC URLs to your development environment. These URLs are essential for connecting your application to the Rootstock network and interacting with smart contracts. From a67e45e551680c540ffe9483fae7d9e44bdf60a0 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:06:03 -0500 Subject: [PATCH 07/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index aa05bfa7..b02aae7e 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -127,7 +127,7 @@ forge script script/Deploy.s.sol --rpc-url https://public-node.testnet.rsk.co -- - You can remove the `--broadcast` flag if you wan to simulate the transaction without broadcasting it. ::: -> If you get an error like `Transaction dropped from the mempool: ` or the ```transaction not completed```, check the tx-id in the explorer. The tx may have went successful but the error is still in the logs. Here are the [mainnet](https://explorer.rootstock.io/) and [testnet](https://explorer.testnet.rootstock.io/) explorers. +> If you encounter an error such as `Transaction dropped from the mempool: ` or `transaction not completed`, check the `tx-id` in the explorer. The transaction may have been successful but the error is still within the logs. See the [mainnet](https://explorer.rootstock.io/) and [testnet](https://explorer.testnet.rootstock.io/) explorers for more info. > Also you can see the transaction registry locally, by checking the folder ```broadcast/Deploy.s.sol/``` and opening the file called ```run-latest.json```, if you check the fields, there is one called ```contractAddress``` which contains the new address deployed for our ERC20 smart contract. From f22a37c9cda3b529cebd55d17439827b855d3e1e Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:06:15 -0500 Subject: [PATCH 08/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index b02aae7e..aea888a1 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -129,7 +129,7 @@ forge script script/Deploy.s.sol --rpc-url https://public-node.testnet.rsk.co -- > If you encounter an error such as `Transaction dropped from the mempool: ` or `transaction not completed`, check the `tx-id` in the explorer. The transaction may have been successful but the error is still within the logs. See the [mainnet](https://explorer.rootstock.io/) and [testnet](https://explorer.testnet.rootstock.io/) explorers for more info. -> Also you can see the transaction registry locally, by checking the folder ```broadcast/Deploy.s.sol/``` and opening the file called ```run-latest.json```, if you check the fields, there is one called ```contractAddress``` which contains the new address deployed for our ERC20 smart contract. +> Also you can see the transaction registry locally, by checking the folder `broadcast/Deploy.s.sol/` and opening the file called `run-latest.json`. See the field called `contractAddress` which contains the new address deployed for the ERC20 smart contract. The result should look like this: ```bash From 3873b500d0abb20e6a4341d6541f75b54be01167 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:06:28 -0500 Subject: [PATCH 09/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index aea888a1..7b9250d7 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -150,7 +150,7 @@ Total Paid: 0. ETH (106719 gas * avg 0 gwei) ``` ## Interacting with the Contract - Minting a Token -If the contract is already deployed, then you can interact with it using ```cast``` this command allows you to interact with the contract, in this case, read the balance of an account. +If the contract is already deployed, then you can interact with it using `cast` this command allows you to interact with the contract, in this case, read the balance of an account. ### Reading the Balance of an Account In your terminal, run the following command, replacing the placeholders with actual values: From 119370a27259b48293ad4253fb1f8ff9cca975a0 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:06:40 -0500 Subject: [PATCH 10/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 7b9250d7..4e5651d3 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -75,7 +75,7 @@ There are two ways to obtain RPC URLs: #### Using Public RPC URLs -- Visit the [MetaMask Integration on the Rootstock Dev Portal](/dev-tools/wallets/metamask/). This guide provides instructions on setting up MetaMask for Rootstock. While following these steps, pay close attention to the sections on adding custom networks. You'll find the RPC URLs for Rootstock Testnet and Mainnet listed. +- Visit the [MetaMask Integration on the Rootstock DevPortal](/dev-tools/wallets/metamask/). This guide provides instructions on setting up MetaMask for Rootstock. While following these steps, pay close attention to the sections on adding custom networks. You'll find the RPC URLs for Rootstock Testnet and Mainnet listed. #### Using RPC API - Create an account at the [Rootstock RPC API](https://rpc.rootstock.io/). Once logged in, navigate to your dashboard and copy the API Key. From cb594937094ebbd19b944da3adbf73c0b17e6301 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:06:55 -0500 Subject: [PATCH 11/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 4e5651d3..dac6f74b 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -78,7 +78,7 @@ There are two ways to obtain RPC URLs: - Visit the [MetaMask Integration on the Rootstock DevPortal](/dev-tools/wallets/metamask/). This guide provides instructions on setting up MetaMask for Rootstock. While following these steps, pay close attention to the sections on adding custom networks. You'll find the RPC URLs for Rootstock Testnet and Mainnet listed. #### Using RPC API -- Create an account at the [Rootstock RPC API](https://rpc.rootstock.io/). Once logged in, navigate to your dashboard and copy the API Key. +- Create an account on the [Rootstock RPC API](https://rpc.rootstock.io/). Once logged in, navigate to your dashboard and copy the API Key. ### Adding environment variables to your project From 8cdf9961a972471657a5fad47a448cf294b61d02 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:07:04 -0500 Subject: [PATCH 12/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index dac6f74b..5326402c 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -165,4 +165,4 @@ The result should look like this: ## Final Comments -Explore and be curious about the folders and files of this starter kit. You'll learn how to import `.env` variables for deploying smart contracts, test smart contracts with solidity. Feel free to customize this starter kit to suit your project’s needs. Happy coding! \ No newline at end of file +You can explore the folders and files within the starter kit and customize the kit to suit your project’s needs. You can also learn how to import `.env` variables for deploying smart contracts, test smart contracts with solidity, etc. \ No newline at end of file From e260353a1c41dc84f85bcff15af55ed4b450cd47 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:08:39 -0500 Subject: [PATCH 13/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 5326402c..c80d3c41 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -87,7 +87,10 @@ After obtaining the RPC URLs, create a file named `.env` in your project's root ``` PRIVATE_KEY: Your private key (e.g., from your Metamask account details). ``` -**_NOTE: Make sure the private key you paste, starts with 0x, if does not contain it, please put 0x before your private key. (0x123...)_** +:::tip[Tip] +Ensure the private key copied starts with `0x123...` +::: + ## Running tests to an ERC20 Token Contract This section runs tests on an ERC20 token contract (fungible token), this is done according to the script located at ```test/Erc20Token.t.sol```. It does test deployment, minting, and transfer of tokens. From 2e8b9e7d57e0c6800277b37eebd56dc2f81c50e4 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:08:52 -0500 Subject: [PATCH 14/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index c80d3c41..1fd17aa9 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -93,7 +93,7 @@ Ensure the private key copied starts with `0x123...` ## Running tests to an ERC20 Token Contract -This section runs tests on an ERC20 token contract (fungible token), this is done according to the script located at ```test/Erc20Token.t.sol```. It does test deployment, minting, and transfer of tokens. +This section runs tests on an ERC20 token contract (fungible token), this is done according to the script located at `test/Erc20Token.t.sol`. It does test deployment, minting, and transfer of tokens. For this, run the next forge command: From 1bdd617d67fad5c851cbbe5e60c79f5019036527 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:09:06 -0500 Subject: [PATCH 15/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 1fd17aa9..61603f21 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -92,7 +92,7 @@ Ensure the private key copied starts with `0x123...` ::: -## Running tests to an ERC20 Token Contract +## Running tests on an ERC20 Token Contract This section runs tests on an ERC20 token contract (fungible token), this is done according to the script located at `test/Erc20Token.t.sol`. It does test deployment, minting, and transfer of tokens. For this, run the next forge command: From c39fa518d633ff808e267e40b19c81e8c63b2321 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:09:20 -0500 Subject: [PATCH 16/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 61603f21..59f69e27 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -116,7 +116,7 @@ Ran 1 test suite in 143.90ms (8.73ms CPU time): 2 tests passed, 0 failed, 0 skip **_NOTE: If you need additional tests, or want to go deep on this step, visit the [Foundry Tests Documentation](https://book.getfoundry.sh/forge/tests)._** ## Deploying an ERC20 Token Contract -This section deploys an ERC20 token contract (fungible token) on the Rootstock network. This contract is located at ```src/Erc20Token.sol``` file, it uses the script located at ```script/Deploy.s.sol``` for this operation. +This section deploys an ERC20 token contract (fungible token) on the Rootstock network. This contract is located at `src/Erc20Token.sol` file, it uses the script located at `script/Deploy.s.sol` for this operation. Run the following command, replacing `https://public-node.testnet.rsk.co` with either `rskTestnet` or `rskMainnet` rpc url if you have, depending on your desired deployment environment: From 7df615a21838d50c5553f757d888ab41c165d203 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:10:25 -0500 Subject: [PATCH 17/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 59f69e27..3e492352 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -127,7 +127,7 @@ forge script script/Deploy.s.sol --rpc-url https://public-node.testnet.rsk.co -- - [EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md) is not supported or not activated on the Rootstock RPC url - The `--legacy` flag is passed to use legacy transactions instead of `EIP-1559`. -- You can remove the `--broadcast` flag if you wan to simulate the transaction without broadcasting it. +- You can remove the `--broadcast` flag if you want to simulate the transaction without broadcasting it. ::: > If you encounter an error such as `Transaction dropped from the mempool: ` or `transaction not completed`, check the `tx-id` in the explorer. The transaction may have been successful but the error is still within the logs. See the [mainnet](https://explorer.rootstock.io/) and [testnet](https://explorer.testnet.rootstock.io/) explorers for more info. From 135c808941c645dc94b4794f5f59f0eebfae48ec Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:11:12 -0500 Subject: [PATCH 18/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 3e492352..5c24ad69 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -10,6 +10,8 @@ Whether you’re a seasoned developer or just starting your journey into smart c Rootstock is fully EVM (Ethereum Virtual Machine) compatible. It brings the power of smart contracts to Bitcoin, allowing developers to leverage Bitcoin’s security while benefiting from Ethereum’s ecosystem. +In this tutorial, you'll learn how to set up your Foundry development environment, connect to a Rootstock network, write and test smart contracts, deploy them to the Rootstock blockchain, and interact with them. We'll guide you through every step, from installation to minting your first token. + ## Prerequisites Before starting the dApp, make sure to have the following prerequisites: From 381365ca7b4eea594416ef14a7e72b129d80bdb1 Mon Sep 17 00:00:00 2001 From: Sebas <157399509+SebasGuaquetaRSK@users.noreply.github.com> Date: Fri, 11 Oct 2024 10:09:19 -0500 Subject: [PATCH 19/19] Update docs/02-developers/04-quickstart/foundry.md Co-authored-by: Owanate Amachree --- docs/02-developers/04-quickstart/foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-developers/04-quickstart/foundry.md b/docs/02-developers/04-quickstart/foundry.md index 5c24ad69..74be0851 100644 --- a/docs/02-developers/04-quickstart/foundry.md +++ b/docs/02-developers/04-quickstart/foundry.md @@ -120,7 +120,7 @@ Ran 1 test suite in 143.90ms (8.73ms CPU time): 2 tests passed, 0 failed, 0 skip ## Deploying an ERC20 Token Contract This section deploys an ERC20 token contract (fungible token) on the Rootstock network. This contract is located at `src/Erc20Token.sol` file, it uses the script located at `script/Deploy.s.sol` for this operation. -Run the following command, replacing `https://public-node.testnet.rsk.co` with either `rskTestnet` or `rskMainnet` rpc url if you have, depending on your desired deployment environment: +Run the following command, replacing `https://public-node.testnet.rsk.co` with either `rskTestnet` or `rskMainnet` rpc url if you have the testnet and mainnet environments configured for your desired deployment environment, for this guide, we will use the public node url: ```bash forge script script/Deploy.s.sol --rpc-url https://public-node.testnet.rsk.co --broadcast --legacy