Change Details

npm start 1. send a normal XEC tx with no message to ensure no regression 2. send an unencrypted message from wallet A to wallet B, ensure no regression and both wallets can view the message in tx history 3. send an encrypted message from wallet A to wallet B, ensure only wallet B can view the decrypted message in tx history 4. send a short 3 character message in encrypted mode to wallet B 5. send a long 94 character message in encrypted mode to wallet B 6. input a 160 character message in unencrypted mode then switch to encrypted mode and ensure the input is truncated up to the allowed 94 character limit. Send this message and ensure the underlying message sent is the 94 character message. 7. Repeat step 5 except send it in unencrypted form and ensure the full 160 characters is sent despite switching to the truncated encrypted view. 8. send an encrypted message to a newly created wallet with no transactions and ensure the 'No transaction history' error is displayed. 9. send an encrypted message to a newly created wallet with incoming transactions but no outbound transactions and ensure the 'No outgoing transactions found in the recipient address' error is displayed. 10. send an encrypted message from wallet A to wallet A, ensure wallet A can view an encrypted message to itself in tx history 11. switch to multiple recipients mode and ensure the encryption switch and the alert is not rendered 12. send multi recipient tx and ensure no unintended encryption 13. check the TX ID for one of the above encrypted messages in blockchain, abc explorer and be.cash explorer, and ensure the message is not legible

npm start 1. send a normal XEC tx with no message to ensure no regression 2. send an unencrypted message from wallet A to wallet B, ensure no regression and both wallets can view the message in tx history 3. send an encrypted message from wallet A to wallet B, ensure only wallet B can view the decrypted message in tx history 4. send a short 3 character message in encrypted mode to wallet B 5. send a long 94 character message in encrypted mode to wallet B 6. input a 160 character message in unencrypted mode then switch to encrypted mode and ensure the input is truncated up to the allowed 94 character limit. Send this message and ensure the underlying message sent is the 94 character message. 7. Repeat step 5 except send it in unencrypted form and ensure the full 160 characters is sent despite switching to the truncated encrypted view. 8. send an encrypted message to a newly created wallet with no transactions and ensure the 'No transaction history' error is displayed. 9. send an encrypted message to a newly created wallet with incoming transactions but no outbound transactions and ensure the 'No outgoing transactions found in the recipient address' error is displayed. 10. use the newly created wallet to send an outbound XEC transaction. Then ensure wallet A is able to now successfully send an encrypted message to this newly created wallet. 11. send an encrypted message from wallet A to wallet A, ensure wallet A can view an encrypted message to itself in tx history 12. switch to multiple recipients mode and ensure the encryption switch and the alert is not rendered 13. send multi recipient tx and ensure no unintended encryption 14. check the TX ID for one of the above encrypted messages in blockchain, abc explorer and be.cash explorer, and ensure the message is not legible

npm start 1. send a normal XEC tx with no message to ensure no regression 2. send an unencrypted message from wallet A to wallet B, ensure no regression and both wallets can view the message in tx history 3. send an encrypted message from wallet A to wallet B, ensure only wallet B can view the decrypted message in tx history 4. send a short 3 character message in encrypted mode to wallet B 5. send a long 94 character message in encrypted mode to wallet B 6. input a 160 character message in unencrypted mode then switch to encrypted mode and ensure the input is truncated up to the allowed 94 character limit. Send this message and ensure the underlying message sent is the 94 character message. 7. Repeat step 5 except send it in unencrypted form and ensure the full 160 characters is sent despite switching to the truncated encrypted view. 8. send an encrypted message to a newly created wallet with no transactions and ensure the 'No transaction history' error is displayed. 9. send an encrypted message to a newly created wallet with incoming transactions but no outbound transactions and ensure the 'No outgoing transactions found in the recipient address' error is displayed. 10. send an encrypuse the newly created message from wallet A to wallet A,wallet to send an outbound XEC transaction. Then ensure wallet A can viewis able to now successfully send an encrypted message to itself in tx historythis newly created wallet. 11. switch to multiple recipients mode andsend an encrypted message from wallet A to wallet A, ensure the encryption switch and the alert is not renderedwallet A can view an encrypted message to itself in tx history 12. sendswitch to multiple recipient txs mode and ensure no unintended encryptionthe encryption switch and the alert is not rendered 13. send multi recipient tx and ensure no unintended encryption 14. check the TX ID for one of the above encrypted messages in blockchain, abc explorer and be.cash explorer, and ensure the message is not legible