Deploy OCR Contract
From Chainlink Community Wiki
This Page will provide the information necessary to deploy an OCR Aggregator.
Process Overview:
The below is a high level overview of the process.
In the section after this one, Detailed Contract Deployment Instructions, you'll find links to other pages with in depth details and examples.
- Deploy two
SimpleWriteAccessController.sol
contracts- One will be used as your
_BILLINGACCESSCONTROLLER
- This Contract controls which addresses have the access to update the OCR billing values
- The other will be used as your
_REQUESTERACCESSCONTROLLER
- This Contract controls which addresses have access to respond to the OCR contract (It whitelists the Nodes)
- One will be used as your
- Be sure to track which of the contract addresses you'll use for each purpose.
- With the SimpleWtriteAccessController.sol contract deployed, we will then be able to deploy the OCR Aggregator contract., or the
AccessControlledOffchainAggregator.sol
contract- The contract is available, in it's flattened version, here
- When deploying the
AccessControlledOffchainAggregator.sol
contract, you'll need to specify the below constructor variables (for details, see the below section)_MAXIMUMGASPRICE
_REASONABLEGASPRICE
_MICROLINKPERETH
_LINKGWEIPEROBSERVATION
_LINKGWEIPERTRANSMISSION
_LINK
_MINANSWER
_MAXANSWER
_BILLINGACCESSCONTROLLER
_REQUESTERACCESSCONTROLLER
_DECIMALS
DESCRIPTION
- Once you have deployed the
AccessControlledOffchainAggregator.sol
contract, you'll need to update additional variables to enable the Chainlink Nodes to submit their observations.- you can find specific instructions to accomplish this in the section below.
Detailed Contract Deployment Instructions
Deploy Two SimpleWriteAccessController.sol contracts
|
---|
Deploy AccessControlledOffchainAggregator.sol contract
|
Add your Chainlink Nodes to the Offchain Aggregator |
Update The Offchain Aggregator's Billing Values |