AccessControlledAggregator Verification
From Chainlink Community Wiki
Verifying An AccessControlledAggregator
The instructions in this example will contain an exampleFluxMonitor contract on Rinkeby, but the directions will be equally applicable to any network that uses an etherscan-based explorer.
https://rinkeby.etherscan.io/address/0x30f3e33D93C79572642B89C631Df3D180dd965Bf#code
Set Base Variables for Verifying the Contract
Navigate the your deployed contract's address in Etherscan, then click on the Contract tab.
If the contract is not verified, then you will see a page with the contract's ByteCode and an option to "Verify and Publish" the contract.
We'll go ahead and click on "Verify and Publish", which takes us to a new page.
Here we will want to confirm the contract's address, set the compiler type to Solidity (Single file), and then set the Compiler Version to 0.6.6+commit.6c089d02.
Lastly, since Chainlink uses the MIT License (MIT), we'll want to select that as well.
Then click "Continue"
Copy Over the Source Code of the Contract
Once on the next page, be sure to open the drop-down for "Optimization" and set it to Yes.
The AccessControlledAggregator.sol source code is available in the drop down below:
Expand
AccessControlledAggregator Source Code (Expand option is to the right --->)
Copy the contents on that page and paste it into the empty field titled "Enter the Solidity Contract Code below"
Copy in the Constructor Arguments
You do not need to provide the constructor arguments for the AccessControlledAggregator contract, since we did not set any values when deploying the contract.
Set Miscellaneous Settings
Click the drop-down for Misc. Settings and set the Runs to 1000000 (one million)
Leave the other options as their defaults.
Once you have the above completed, click the button to verify the contract.