5.1 KiB
Setup Mainnet Fork Environment
Interact with InstaDApp DSA using Forked Mainnet from your local network
When you want to interact with contracts that are deployed on the Ethereum mainnet for development purpose without spending any ether you can fork the mainnet from a particular block number and then interact with that forked mainnet on your local machine.
So, today we will take a look at how you can fork the mainnet and interact with DSA contracts and spells.
Step 1: Forking the Ethereum Mainnet
Open terminal and run:
ganache-cli --fork https://mainnet.infura.io/v3/{Project_Id} --unlock {Ethereum_Address} -p {Port_Number} --networkId 1
| Parameters | |
|---|---|
| {Project_Id} | This Id comes from infura. If you don’t know about how to get this, just open infura and create a free account. After creating account add a new project and you will get the Project_Id that you need. Sample Project_Id has been shown in the image. |
| {Ethereum_Address} | On forked mainnet you can unlock any account of your choice without knowing their private key. So, let’s say you want to test something which requires transaction of DAI or other coin. So, you can choose an account which has lots of DAI. This way you can unlock any account of your choice. |
| {Port_Number} | It is the port number on which you want to run the ganache-cli. The default port number for ganache-cli is 8545 |
If you want to fork mainnet at a particular block number you can do that by providing value of Block_Number after infura Project_ID
ganache-cli --fork https://mainnet.infura.io/v3/{Project_Id}@{Block_Number} --unlock {Ethereum_Address} -p {Port_Number} --networkId 1
After running the command, it will fork the mainnet for you and it will return you something like this:
And as you can see it is mentioning that it is Forked Chain and also provides details about chain like Block number you forked that mainnet from and also the network id.
Note: If Block’s value in the Forked Chain characteristics is ‘0’ then it means that you have not been able to fork the chain properly.
Step 2: Interacting with DSA
Create a new Directory on your machine and Clone this repo on your machine.
After cloning run javascript npm install in the cloned repo directory.
Before interacting with DSA make sure you have configured .env file which contains the private key, Ethereum address and Infura project Id.
Now, open dsa.js file and check if the port number of your ganache-cli matches with the web3 providers.
Now, you can interact with the DSA by using the dsa.js file. If you don’t have any DSA account you can create one by uncommenting this section from dsa.js file.
The file contains a section where you can add your spells by default it contains spells for deposit and withdraw methods of Compound Connector.
File also contains methods for account setup and transfer.
Step 3: Executing the file
After making all the changes in the file execute the file using command:
node dsa.js
This may take few minutes as ganache has to fetch contracts from mainnet and then work on them so be patient, if you want to know if it has stuck or not then head to the tab on console where the ganache-cli is working and check if it is making some calls.
If you are using the default dsa.js file then output will contain dsa accounts linked to your ethereum address and transaction hashthat dsa.cast() function returns
To check the transaction receipt you can follow these steps:
Step 1: Open another terminal tab
Step 2 (make sure you have truffle installed on your machine): run:
truffle console
Step 3: In the truffle console, run:
receipt = await web3.eth.getTransactionReceipt({txHash})
This will return you something like this, if your transaction went through.
Additional advice
If you want to use any particular token then you can unlock address which holds that token and you can get list of all token holders on ethplorer.
If you encounter error saying : “Error: Returned error: Returned error: project ID does not have access to archive state”. Trying reloading the ganache-cli as this will most probably fix this.
Note: This is not the best way to interact with DSA as you might face a lot of errors in the process of interacting on forked mainnet. The best way is still the Ethereum Mainnet.