Deploy Protocol Contracts to new chains

[Ashar2shahid]

The protocol contracts have been deployed and verified on block explorers to the following chains:

linea:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

linea-goerli-testnet:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

mantle:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

mantle-goerli-testnet:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

base:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

base-goerli-testnet:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

polygon-zkevm:
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

polygon-zkevm-testnet(block explorer is currently broken):
AccessControlRegistry
AirnodeRrpV0
AirnodeRrpV0DryRun
RequesterAuthorizerWithAirnode

This cannot be merged until api3dao/chains#64 is merged

[Ashar2shahid]

@andreogle can you take a look at api3dao/chains#64 and publish the package once merged so I can then make this ready for review ?

[andreogle]

fyi, ChainAPI has received a request to support Polygon zkEVM (mainnet and testnet). Once this PR is merged, the above networks will also be added to ChainAPI

[dcroote]

@Ashar2shahid - shouldn't the "Verify Protocol Deployments" CI workflow have run here given all of the new packages/airnode-protocol paths?

[Ashar2shahid]

@Ashar2shahid - shouldn't the "Verify Protocol Deployments" CI workflow have run here given all of the new packages/airnode-protocol paths?

@dcroote yes it should have executed for this PR, strange that it didn't trigger. I will look into it.

update: @dcroote I pushed the following PR to address the CI issue: #1865

[dcroote]

Looks good, one minor question: mantle deployments are deterministic but mantle-goerli-testnet aren't? (Here is the CI run for reference)

[Ashar2shahid]

@dcroote mantle-testnet desterminstic deployments were failing because I suspect the factory isn't deployed there: https://explorer.testnet.mantle.xyz/address/0x4e59b44847b379578588920cA78FbF26c0B4956C/transactions#address-tabs . When hardhat attempts to deploy it, I kept getting this error:

NETWORK=mantle-goerli-testnet yarn deploy:deterministic
yarn run v1.22.19
$ DETERMINISTIC=true hardhat deploy --network $NETWORK --tags deploy && yarn run deploy:generate-references
Nothing to compile
sending eth to create2 contract deployer address (0x3fab184622dc19b6109349b94811493bf2a45362) (tx: 0xeb71a5d76e5b4295e79c2bb9da530758905b43b99a8a2fe828e0974728c9424c)...
deploying create2 deployer contract (at 0x4e59b44847b379578588920ca78fbf26c0b4956c) using deterministic deployment (https://github.com/Arachnid/deterministic-deployment-proxy)An unexpected error occurred:

Error: ERROR processing /Users/ashar/Desktop/API3/Ubuntu/airnode/packages/airnode-protocol/deploy/1_deploy.js:
ProviderError: gas price too high: 100000000000 wei, use at most tx.gasPrice = 1 wei

I tried with minimal gas price but it kept failing

[dcroote]

Not sure what the issue is with the create2 deployer contract at 0x4e59b44847b379578588920ca78fbf26c0b4956c, but it's absence looks like the issue. Transient gas issues? Otherwise, while it's not ideal, this wouldn't be the first chain with nondeterministic deployments and we now have functionality where these addresses don't need to be manually specified in the config as of v0.12 so it's even less of an issue.

[bbenligiray]

Our current protocol is try deterministic deployments with hardhat-deploy, if it doesn't work, deploy undeterministically, so this is fine. (Same with contract verification, try verifying the contract with hardhat-etherscan, if it doesn't work, don't verify.)