Context and scope
Currently the send and sendAndCall interfaces of the bridge contracts both support single and multi-hop transfers. The information needed for both cases is provided in the SendTokensInput and SendAndCallInput. However, this results in some field of the respective inputs being unused in the single-hop case.
Discussion and alternatives and Open questions
Would splitting those interface into two (ie. send and sendMultiHop) allow for more clear usage and cleaner implementation?
Context and scope Currently the
sendandsendAndCallinterfaces of the bridge contracts both support single and multi-hop transfers. The information needed for both cases is provided in theSendTokensInputandSendAndCallInput. However, this results in some field of the respective inputs being unused in the single-hop case.Discussion and alternatives and Open questions Would splitting those interface into two (ie.
sendandsendMultiHop) allow for more clear usage and cleaner implementation?