Add config for chiado gnosis testnet

[jmederosalvarado]

Changes:

• Adds config for what will be gnosis first public testnet with merge support, named chiado

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe): Config

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests??

• Yes
• No

[MarekM25]

Could you add chainspec? What's about denver network?

[LukaszRozmej]

FastBlocks and AllowAuRaPrivateChains are probably to be removed?

[LukaszRozmej]

Should they be added to some tests?

[MarekM25]

@jmederosalvarado fix the runner tests ;)

[dapplion]

Why has this contract to be specified here?

[jmederosalvarado]

I copied it from here. is it not being used or smth?

[dapplion]

You tell me, all I know is that AuRa has many different contracts but only this one is specified here. I don't know the internals of Nethermind, nor which contracts have to be specified here and for what reason

[LukaszRozmej]

So priorities contract is used for potentially sorting transactions when creating blocks. Priorities can come from contract or local configuration. Priorities are optional. Not sure if you deployed this contract on denver. More information can be found here: #2300

[jmederosalvarado]

Also. I see here that you have a contract deployed to this address in denver genesis. That's what is being used as TxPriorityContract in denver.

[dapplion]

Got it, thanks!