Skip to content
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.

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

feat(connector-Besu) Load contract instances from compiled contract files #612

Closed
kikoncuo opened this issue Mar 1, 2021 · 3 comments · Fixed by #671
Closed

feat(connector-Besu) Load contract instances from compiled contract files #612

kikoncuo opened this issue Mar 1, 2021 · 3 comments · Fixed by #671
Assignees
Milestone

Comments

@kikoncuo
Copy link
Contributor

kikoncuo commented Mar 1, 2021

Parent: feat(cactus): Standardized common interface functionality transaction across connectors #604
This is a dependency for #609

Description:
Using the .json files generated from compiling a Solidity smart contract, the Besu/Quorum connector plugin should be able to load web3 smart contract instances in the constructors, write them using the keystore plugin, store them in a map and use them to generate the transactions simplifying the usage vs providing the abi in a per transaction basis.

Acceptance criteria:

  • Contracts are loaded from a folder and invokable by using their contract name.
@jordigiam
Copy link

jordigiam commented Mar 2, 2021

Working in this

@kikoncuo kikoncuo assigned kikoncuo and jordigiam and unassigned kikoncuo Mar 2, 2021
@AzaharaC
Copy link
Contributor

Working on this.

@AzaharaC
Copy link
Contributor

To solve this task, we need to modify the deploy function to update the networks field in the compiled contract .json file, like other SDKs do (https://trufflesuite.github.io/artifact-updates/requirements/truffle.html). This is necessary to recover the contract instance deployed on the blockchain from the compiled contract file.

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

Successfully merging a pull request may close this issue.

3 participants