embarklabs / embark

Framework for serverless Decentralized Applications using Ethereum, IPFS and other platforms

Home Page:https://framework.embarklabs.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add chainId and/or networkName to the JSON Artifact

kamescg opened this issue · comments

Feature Request

Using the embark new [dApp] --contracts-only boilerplate. I Only require embark to build and deploy my smart contracts.

The artifacts, after they are deployed, are migrated to an existing decentralized application frontend. That frontend auto-imports contract via the JSON file and initializes the contract by detecting what network the contract was deployed on.

From what I can tell the artifact does not include the chainId or networkName and thus my application is unable to detect what network the contract should connect with.

Summary

Can the chainId and/or networkName be added to the artifact.

Thank you 😄

Sounds quite reasonable. I'll pass it on to the team.
Thanks for the suggestion!