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
__For Windows users we highly recommend using [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) or Git Bash as your terminal app.__
210
-
211
-
## Start Here
212
-
Run the following commands in your terminal:
213
-
\`\`\`bash
214
-
yarn install
215
-
foundryup
216
-
\`\`\``,
217
-
BOTTOM_CONTENT: `## Testing Your Progress
218
-
Use your skills to build out the above requirements in whatever way you choose. You are encouraged to run tests periodically to visualize your progress.
219
-
220
-
Run tests using \`yarn foundry:test\` to run a set of tests against the contract code. Initially you will see build errors but as you complete the requirements you will start to pass tests. If you struggle to understand why some tests are returning errors then you might find it useful to run the command with the extra logging verbosity flag \`-vvvv\` (\`yarn foundry:test -vvvv\`) as this will show you very detailed information about where tests are failing. Learn how to read the traces [here](https://book.getfoundry.sh/forge/traces). You can also use the \`--match-test "TestName"\` flag to only run a single test. Of course you can chain both to include a higher verbosity and only run a specific test by including both flags \`yarn foundry:test -vvvv --match-test "TestName"\`. You will also see we have included an import of \`console2.sol\` which allows you to use \`console.log()\` type functionality inside your contracts to know what a value is at a specific time of execution. You can read more about how to use that at [FoundryBook](https://book.getfoundry.sh/reference/forge-std/console-log).
221
-
222
-
For a more "hands on" approach you can try testing your contract with the provided front end interface by running the following:
223
-
\`\`\`bash
224
-
yarn chain
225
-
\`\`\`
226
-
in a second terminal deploy your contract:
227
-
\`\`\`bash
228
-
yarn deploy
229
-
\`\`\`
230
-
in a third terminal start the NextJS front end:
231
-
\`\`\`bash
232
-
yarn start
233
-
\`\`\`
234
-
235
-
## Solved! (Final Steps)
236
-
Once you have a working solution and all the tests are passing your next move is to deploy your lovely contract to the Sepolia testnet.
237
-
First you will need to generate an account. **You can skip this step if you have already created a keystore on your machine. Keystores are located in \`~/.foundry/keystores\`**
238
-
\`\`\`bash
239
-
yarn account:generate
240
-
\`\`\`
241
-
You can optionally give your new account a name be passing it in like so: \`yarn account:generate NAME-FOR-ACCOUNT\`. The default is \`scaffold-eth-custom\`.
242
-
243
-
You will be prompted for a password to encrypt your newly created keystore. Make sure you choose a [good one](https://xkcd.com/936/) if you intend to use your new account for more than testnet funds.
244
-
245
-
Now you need to update \`packages/foundry/.env\` so that \`ETH_KEYSTORE_ACCOUNT\` = your new account name ("scaffold-eth-custom" if you didn't specify otherwise).
246
-
247
-
Now you are ready to send some testnet funds to your new account.
248
-
Run the following to view your new address and balances across several networks.
249
-
\`\`\`bash
250
-
yarn account
251
-
\`\`\`
252
-
To fund your account with Sepolia ETH simply search for "Sepolia testnet faucet" on Google or ask around in onchain developer groups who are usually more than willing to share. Send the funds to your wallet address and run \`yarn account\` again to verify the funds show in your Sepolia balance.
253
-
254
-
Once you have confirmed your balance on Sepolia you can run this command to deploy your contract.
255
-
\`\`\`bash
256
-
yarn deploy:verify --network sepolia
257
-
\`\`\`
258
-
This command will deploy your contract and verify it with Sepolia Etherscan.
259
-
Copy your deployed contract address from your console and paste it in at [sepolia.etherscan.io](https://sepolia.etherscan.io). You should see a green checkmark on the "Contract" tab showing that the source code has been verified.
260
56
261
-
Now you can return to the ETH Tech Tree CLI, navigate to this challenge in the tree and submit your deployed contract address. Congratulations!`
constbottomMenuText=chalk.bold(`${borderLeft}${chalk.bgBlue(`<q>`)} to quit | ${chalk.bgBlue(`<Esc>`)} to go back | ${chalk.bgBlue(`<p>`)} view progress | ${chalk.bgBlue(`<l>`)} leaderboard${newArray(width-72).fill(border).join('')}${borderRight}`);
403
+
constbottomMenuText=chalk.bold(`${borderLeft}${chalk.bgBlueBright(`<q>`)} to quit | ${chalk.bgBlueBright(`<Esc>`)} to go back | ${chalk.bgBlueBright(`<p>`)} view progress | ${chalk.bgBlueBright(`<l>`)} leaderboard${newArray(width-72).fill(border).join('')}${borderRight}`);
404
404
405
405
// Save cursor position
406
406
process.stdout.write('\x1B7');
@@ -446,13 +446,13 @@ Open up the challenge in your favorite code editor and follow the instructions i
0 commit comments