File tree 1 file changed +2
-2
lines changed
1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -38,7 +38,7 @@ The concept of cheat codes and cheat code inspector is very simple.
38
38
39
39
In solidity cheat codes are calls to a specific address, the cheat code handler address:
40
40
41
- ` keccak( ` address(bytes20(uint160(uint256(keccak256('hevm cheat code')))))` ) ` : 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D
41
+ ` keccak(address(bytes20(uint160(uint256(keccak256('hevm cheat code')))))) ` : 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D
42
42
43
43
which can be initialized like ` Cheats constant cheats = Cheats(0x7109709ECfa91a80626fF3989D68f67F5b1DD12D); ` , when
44
44
inheriting from ` forge-std/Test.sol ` it can be accessed via ` vm.<cheatcode> ` directly.
@@ -83,7 +83,7 @@ essentially a large `match` over the decoded `HEVMCalls` which serves as the imp
83
83
84
84
## Adding a new cheat code
85
85
86
- This process consists of 3 steps:
86
+ This process consists of 4 steps:
87
87
88
88
1 . add the function signature to the ` abigen! ` macro so a new ` HEVMCalls ` variant is generated
89
89
2 . implement the cheat code handler
You can’t perform that action at this time.
0 commit comments