Skip to content

Commit d22e107

Browse files
committed
improve instructions
1 parent 5be4286 commit d22e107

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

README.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,24 +14,25 @@ Use Damn Vulnerable DeFi to:
1414
## Install
1515

1616
1. Clone the repository.
17-
2. Checkout the latest release.
17+
2. Checkout the latest release (for example, `git checkout v4.0.0`)
1818
3. Rename the `.env.sample` file to `.env` and add a valid RPC URL. This is only needed for the challenges that fork mainnet state.
1919
4. Either install [Foundry](https://book.getfoundry.sh/getting-started/installation), or use the [provided devcontainer](./.devcontainer/) (In VSCode, open the repository as a devcontainer with the command "Devcontainer: Open Folder in Container...")
20+
5. Run `forge build` to initialize the project.
2021

2122
## Usage
2223

2324
Each challenge is made up of:
2425

25-
- A prompt located in `src/challenge-name/README.md`.
26-
- A set of contracts located in `src/challenge-name/`.
27-
- A [Foundry test](https://book.getfoundry.sh/forge/tests) located in `test/challenge-name/ChallengeName.t.sol`.
26+
- A prompt located in `src/<challenge-name>/README.md`.
27+
- A set of contracts located in `src/<challenge-name>/`.
28+
- A [Foundry test](https://book.getfoundry.sh/forge/tests) located in `test/<challenge-name>/<ChallengeName>.t.sol`.
2829

2930
To solve a challenge:
3031

3132
1. Read the challenge's prompt.
3233
2. Uncover the flaw(s) in the challenge's smart contracts.
3334
3. Code your solution in the corresponding test file.
34-
4. Try your solution with `forge test --match-contract ChallengeName`.
35+
4. Try your solution with `forge test --mp test/<challenge-name>/<ChallengeName>.t.sol`.
3536
If the test passes, you've solved the challenge!
3637

3738
Challenges may have more than one possible solution.

0 commit comments

Comments
 (0)