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
Copy file name to clipboardExpand all lines: lazer/contracts/evm/README.md
+24-11Lines changed: 24 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -9,39 +9,52 @@ This package is built using [Foundry](https://book.getfoundry.sh/).
9
9
### Build
10
10
11
11
```shell
12
-
$ forge build
12
+
forge build
13
13
```
14
14
15
15
### Test
16
16
17
17
```shell
18
-
$ forge test
18
+
forge test
19
19
```
20
20
21
21
### Format
22
22
23
23
```shell
24
-
$ forge fmt
24
+
forge fmt
25
25
```
26
26
27
27
### Gas Snapshots
28
28
29
29
```shell
30
-
$ forge snapshot
30
+
forge snapshot
31
31
```
32
32
33
33
### Anvil
34
34
35
35
Anvil does not come with CreateX by default. It can be deployed or an RPC which has the contract can be forked. The below command forks an RPC with a functional CreateX contract.
Run the following commands to deploy the `PythLazer` contract to the target network. For the verification to work, you need to provide an API key (which is
44
+
etherscan most of the times). If you can't make it work, you can always deploy the contract without verification and verify it manually later (using the
Then, run the following command to add the trusted signer to the `PythLazer` contract. The trusted signer is the address of the Pyth Lazer payload signer, and
53
+
the expiration timestamp is the time when the signer will no longer be trusted.
0 commit comments