livepeer / livepeer/verification-computation-solver
Use contract abi instead of Truffle artifact?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently storing a Truffle artifact and loading the contract abi from it to pass to `web3.eth.contract`. Maybe we should just store the abi instead since we are not using any of the other fields in the Truffle artifact file and are just using web3 directly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Truffle artifact loading and the web3.eth.contract setup, then inspect how the contract ABI is stored or generated. Confirm which artifact fields are used and verify that contract event monitoring still works after switching to the ABI directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, blockchain
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100