Teleporter contracts adaptation for receiving messaging using arbitrary protocols #865
Description
Once the design from #863 is firmed up, the Teleporter contracts will need to be extended to support receiving messages using the configurable authentication mechanisms. The interface abstractions should be properly designed such that the specific authentication mechanism doesn't need to be known to the receiving contract.
Open question: should a single contract instance support receiving from any chain/using any authentication mechanism (requiring that information to be surfaced to the contract being called by Teleporter), or should it only support a single verification instance implementation?