_encode in setConfig in AccessControlledOffchainAggregator
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- solidity
- Domain
- blockchain, documentation
Research direction
Start at the deployed AccessControlledOffchainAggregator contract and its setConfig entry point. Determine what _encode represents and how callers should construct it, then document the required fields and encoding procedure with a concrete example. No source file or test is identified in the issue.
Written by the indexing model from the issue text.
Description
In the smart contract set for the OffchainReporting, there is in the deployed contract "AccessControllerOffchainAggregator" the field setConfig which asks for _encode.
What do I encode here and how do I encode it?
- Dominant language
- Go
- Stars
- 82
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
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.
More from smartcontractkit/libocr
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
smartcontractkit/libocr#127 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
smartcontractkit/libocr#94 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
smartcontractkit/libocr#87 · 2 reactions ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
smartcontractkit/libocr#34 ·
All issues in smartcontractkit/libocr
Similar issues
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100