Actions

AccessControlledOffchainAggregator Management: Difference between revisions

From Chainlink Community Wiki

(Created page with "This page provides guidance on managing your <code>AccessControlledOffchainAggregator</code> (your OCR aggregator) contract. For the sake of keeping things relatively simple, we'll be using Etherscan to manage the contract. Please see the index to easily navigate between the various sections as there is a lot of information here. == Adding Chainlink Nodes to Your AccessControlledOffchainAggregator ==")
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 6: Line 6:


== Adding Chainlink Nodes to Your AccessControlledOffchainAggregator ==
== Adding Chainlink Nodes to Your AccessControlledOffchainAggregator ==
So you've already deployed your OCR aggregator contract, and now you want to add some Chainlink Nodes to the contract.
In order to accomplish this, we will need some information from your Chainlink Node Operators:
Signing Address
Transmitter Address
Payee Address
OCR Config Public Key
=== '''setConfig Variables''' ===
<code>'''_signers (address[])'''</code> : This is an array of signing addresses for each of the Chainlink Nodes making observations for this OCR Contract.  It is critical that the ordering of the signing addresses and their respective transmitting addresses are identical.
<code>'''_transmitters (address[])'''</code> : This is going to be an array of the the Account Addresses of each Chainlink Node participating in the feed.  It is critical that each node be in the same sequential order as their  respective <code>_signers</code> addresses.
<code>'''_threshold (uint8)'''</code> : This value is the maximum number of failed oracles.  It must be set to (totalNumberOfOracles ÷ 3) - 1 .  It must be encoded as a uint8.  For example on a feed with 10 oracles, you would set it to
<code>'''_encodedConfigVersion (uint64)'''</code> : This is a uint64 encoded value that tracks the version of the config.  It can be set to 1, or as a unit64, <code>0x0000000000000000000000000000000000000000000000000000000000000001</code>
<code>'''_encoded (bytes)'''</code> :

Latest revision as of 17:42, 7 June 2022

This page provides guidance on managing your AccessControlledOffchainAggregator (your OCR aggregator) contract.

For the sake of keeping things relatively simple, we'll be using Etherscan to manage the contract.

Please see the index to easily navigate between the various sections as there is a lot of information here.

Adding Chainlink Nodes to Your AccessControlledOffchainAggregator

So you've already deployed your OCR aggregator contract, and now you want to add some Chainlink Nodes to the contract.

In order to accomplish this, we will need some information from your Chainlink Node Operators:

Signing Address

Transmitter Address

Payee Address

OCR Config Public Key

setConfig Variables

_signers (address[]) : This is an array of signing addresses for each of the Chainlink Nodes making observations for this OCR Contract. It is critical that the ordering of the signing addresses and their respective transmitting addresses are identical.

_transmitters (address[]) : This is going to be an array of the the Account Addresses of each Chainlink Node participating in the feed. It is critical that each node be in the same sequential order as their respective _signers addresses.

_threshold (uint8) : This value is the maximum number of failed oracles. It must be set to (totalNumberOfOracles ÷ 3) - 1 . It must be encoded as a uint8. For example on a feed with 10 oracles, you would set it to

_encodedConfigVersion (uint64) : This is a uint64 encoded value that tracks the version of the config. It can be set to 1, or as a unit64, 0x0000000000000000000000000000000000000000000000000000000000000001

_encoded (bytes) :