Skip to content

refactor(lazer/contracts/evm): update README with more deployment details #2734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 27, 2025
Merged

refactor(lazer/contracts/evm): update README with more deployment details #2734

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 24 additions & 11 deletions lazer/contracts/evm/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,39 +9,52 @@ This package is built using [Foundry](https://book.getfoundry.sh/).
### Build

```shell
$ forge build
forge build
```

### Test

```shell
$ forge test
forge test
```

### Format

```shell
$ forge fmt
forge fmt
```

### Gas Snapshots

```shell
$ forge snapshot
forge snapshot
```

### Anvil

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.

```shell
$ anvil --fork-url "https://eth-sepolia.public.blastapi.io"
anvil --fork-url "https://eth-sepolia.public.blastapi.io"
```

### Deploy

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
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
standard input json format).

```shell
export ETHERSCAN_API_KEY=<your_etherscan_api_key>
forge script script/PythLazerDeploy.s.sol --rpc-url <your_rpc_url> --private-key <your_private_key> --broadcast --verify
```

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
the expiration timestamp is the time when the signer will no longer be trusted.

```shell
$ forge script script/PythLazerDeploy.s.sol --rpc-url <your_rpc_url> --private-key <your_private_key> --broadcast
cast send --rpc-url <your_rpc_url> --private-key <your_private_key> 0xACeA761c27A909d4D3895128EBe6370FDE2dF481 "updateTrustedSigner(address,uint256)" \
"<trusted_signer_address>" "<trusted_signer_expiration_timestamp>"
```

### Upgrade
Expand All @@ -50,19 +63,19 @@ The UUPSUpgradeable feature adds functions to the cocntract which support upgrad
In addition, the private key is necessary or contracts will be deployed to different addresses than expected.

```shell
$ forge script script/PythLazerDeploy.s.sol --rpc-url <your_rpc_url> --private-key <your_private_key> --broadcast --sig "migrate()"
forge script script/PythLazerDeploy.s.sol --rpc-url <your_rpc_url> --private-key <your_private_key> --broadcast --sig "migrate()"
```

### Cast

```shell
$ cast <subcommand>
cast <subcommand>
```

### Help

```shell
$ forge --help
$ anvil --help
$ cast --help
forge --help
anvil --help
cast --help
```
Loading