smartcontractkit / smartcontractkit/libocr

_encode in setConfig in AccessControlledOffchainAggregator

Open
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
82
Forks
64
PR merge metrics
No merged PRs in 30d

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?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
solidity
Domain
blockchain, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.