Skip to content
This repository has been archived by the owner on Nov 28, 2023. It is now read-only.

Challenge adding a different EVM network #3

Open
antonionardella opened this issue Mar 31, 2023 · 1 comment
Open

Challenge adding a different EVM network #3

antonionardella opened this issue Mar 31, 2023 · 1 comment

Comments

@antonionardella
Copy link

antonionardella commented Mar 31, 2023

Hello,

I am attempting to integrate a public EVM testnet into the boilerplate, but I am encountering some obstacles. I have added the necessary RPC and chain_id where required, but I am unsure of the modifications or additions I need to make in the packages/contracts/deployments subfolder for the new chain to be properly recognized.

I would greatly appreciate it if someone could spare the time to guide me on the steps to take and what adjustments need to be made in order to successfully add a new EVM chain.

Here you can see the changes I applied

main...antonionardella:smrathon:main

Thank you

@wottpal
Copy link
Member

wottpal commented Apr 1, 2023

Hey @antonionardella, after you've added the new chain to your frontend environment (w/o the .example ending) the wagmiClient should automatically be configured correctly and deployments.ts looks for the new deployment files from the contracts package. In the contracts package, you need to set up the environment as well, update the hardhat.config.ts accordingly, add a new deploy script for the chain in the package.json, build the contracts and run the deploy ;) Does that help?

Also, please note that I haven't updated this boilerplate in a while (instead focussed more on ink!athon) but it should still all work. 🫡

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants