Up until recently, when conducting a multi-destination transaction, the Console reflected its destination as “Unknown”.
As a result, we performed the following steps:
- Added a new multi-destination type.
- When a multi-destination transaction is now initiated, the destinationType is correct and no longer “none”.
- In the future, we plan to update all historical multi-destination transaction records with the new destinationType.