-
Notifications
You must be signed in to change notification settings - Fork 22
/
Copy pathdeploy.sh
executable file
·42 lines (39 loc) · 1.76 KB
/
deploy.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
#!/bin/bash
# Find process IDs listening on port 8545 (anvil)
anvil=$(lsof -t -i:8545)
# Check if any PIDs were found
if [ -z "$anvil" ]; then
echo "Anvil not running."
else
# Kill the processes
kill $anvil && echo "Terminated running Anvil process."
sleep 3
fi
# start anvil with slots in an epoch send to 1 for faster finalised blocks
anvil --silent --slots-in-an-epoch 1 &
dfx stop
# Find process IDs listening on port 4943 (dfx)
dfx=$(lsof -t -i:4943)
# Check if any PIDs were found
if [ -z "$dfx" ]; then
echo "dfx not running."
else
# Kill the processes
kill $dfx && echo "Terminating running dfx instance."
sleep 3
fi
dfx start --clean --background
dfx ledger fabricate-cycles --icp 10000 --canister $(dfx identity get-wallet)
dfx deploy evm_rpc
cargo build --release --target wasm32-unknown-unknown --package chain_fusion
dfx canister create --with-cycles 10_000_000_000_000 chain_fusion
# because the local smart contract deployment is deterministic, we can hardcode the
# the `get_logs_address` in the initArgument.didd`. in our case we are listening for NewJob events,
# you can read more about event signatures [here](https://docs.alchemy.com/docs/deep-dive-into-eth_getlogs#what-are-event-signatures)
dfx canister install --wasm target/wasm32-unknown-unknown/release/chain_fusion.wasm chain_fusion
# sleep for 3 seconds to allow the evm address to be generated
sleep 3
# save the chain_fusion canisters evm address
export EVM_ADDRESS=$(dfx canister call chain_fusion get_evm_address | awk -F'"' '{print $2}')
# deploy the contract passing the chain_fusion canisters evm address to receive the fees and create a couple of new jobs
forge script script/Coprocessor.s.sol:MyScript --fork-url http://localhost:8545 --broadcast --sig "run(address)" $EVM_ADDRESS