Let's call this DestinationAddressMulti

The original naming convention for the other form item is terrible, should also be changed. Created a task for that.

Split the array once and then assign the other variables.

let addressValueArr = addressArray[i].split(',');
let address = addressValueArr[0]
let value = addressValueArr[1]

Sorry about this one....but.....now that we have sendXec as one function, we no longer need two separate functions for oneToManyXECSend() and oneToOneXECSend()

Instead, a single combined send function should accept the isOneToManyXECSend state variable as a parameter -- then use this parameter for the isolated different workflows (calling sendXec with different parameters, logging separate event in Google Analytics)

Refactor so there is only one function here.

This catch {} block looks identical for both oneToMany === true and oneToMany === false

Please create a new function handleSendXecError(oneToManyFlag) that holds this code and is called in both catch {} blocks..

In the function, the event sent to errorNotification() should depend on oneToMany. If true, errorNotification(e, message, 'Sending XEC one to many'), if false, errorNotification(e, message, 'Sending XEC')

Delete this submit() {} function and just use the above send() function. Use isOneToManyXECSend as the boolean checked inside the send function.

Pass the parameter here as well. If intent is for param to show as not true because it is not passed and therefore undefined, it's okay to just use false -- but in this case might as well stay consistent with the flag.

just a readability quibble

Remove

Use BigNumber here instead of Number to be consistent with rest of function --- we want to always use BigNumber when dealing with XEC or token amounts.

Might also need it if user is sending exceptionally large amounts

Should already be a BigNumber here -- let me know if there was an important reason to do it the other way (keeping it as Number for all the addition, then converting at the end).

This is just being converted back to a string on line 255, then back again to BigNumber in useBCH.js

This should be a string until math operations are performed on it in useBCH.js, so no need to implement BigNumber in this function --- the conversion on L987 in useBCH.js is sufficient