Feat: added chain IDs to injected parameters

[hbarcelos]

Changes

• Added treatment to arbitrableChainID and arbitratorChainID parameters
• Added sandbox for non-browser environments through v8-sandbox
• Added tests for injected parameters

Notice

The changes here are supposed to be backwards compatible, so it will be released as a minor version.

New functionality

As recently discussed on the ERC-1497 original issue, we need some new functionality on @kleros/archon.

The updated proposal introduces, among other things, 2 new fields for the MetaEvidence JSON file:

• arbitrableChainID
• arbitratorChainID

Those fields are important to enable multi-chain MetaEvidence and are crucial in a cross-chain arbitration flow. Furthermore, they prevent issues when using deterministic contract addresses (CREATE2), which could cause a MetaEvidence for a specific chain being considered valid for a different one.

Such parameters can also be injected as scriptParameters when calling archon.arbitrable.getMetaEvidence(), which will be used when the parameters above are not set in the JSON file. However the primary source of truth is still the values declared in the MetaEvidence JSON.

The following table summarizes the behavior when both fields above are present (✅) or absent (❌) in the JSON file and the scriptParameters option:

arbitrableChainID		arbitratorChainID
JSON	params	JSON	params	Description
✅	✅	✅	✅	Invalid if any of the params is different from the values in JSON
✅	✅	✅	❌	Invalid if arbitrableChainID param is different from the value in JSON
✅	✅	❌	✅	Invalid if arbitrableChainID param is different from the value in JSON
✅	✅	❌	❌	Invalid if arbitrableChainID param is different from the value in JSON
✅	❌	✅	✅	Invalid if arbitratorChainID param is different from the value in JSON
✅	❌	✅	❌	Always valid
✅	❌	❌	✅	Always valid
✅	❌	❌	❌	Always valid
❌	✅	✅	✅	Invalid if arbitratorChainID param is different from the value in JSON
❌	✅	✅	❌	Always valid
❌	✅	❌	✅	Always valid
❌	✅	❌	❌	Always valid
❌	❌	✅	✅	arbitrableChainID assumes the same value as arbitratorChainID; invalid if arbitratorChainID param is different from the value in JSON
❌	❌	✅	❌	arbitrableChainID assumes the same value as arbitratorChainID; Always valid
❌	❌	❌	✅	arbitrableChainID assumes the same value as arbitratorChainID; Always valid
❌	❌	❌	❌	Always valid