node / rusk-wallet: Invalid Data error when sending Phoenix transactions

[xevisalle]

Describe the bug
When trying to send Phoenix to another account, we get the error: Rusk error occurred: 500 Internal Server Error: Invalid Data InvalidData.

To Reproduce
The error happens with the last version of both Rusk / rusk-wallet: e21b601
Also happens with the current devnet / testnet. Oldest versions of rusk-wallet face the same issue.

The problem happens locally using the example account: recovery-phrase.txt. Simply try to send a Phoenix transaction and it will fail.

We also tried using dusk.seed in both devnet / testnet with the same error.
Nevertheless, using faucet.seed the transaction seems to get through, although it never gets accepted into a block (probably because we used the same account from different machines and the network is preventing double-spending).

EDIT: we also tried the following:

• convert Phoenix to Moonlight in faucet.seed (works)
• send Moonlight from faucet.seed to faucet-1.seed (works)
• convert Moonlight to Phoenix in faucet-1.seed (works)
• send a Phoenix transaction fromfaucet-1.seed (fails)

Logs/Screenshot

> What would you like to do? Transfer Dusk
> Please enter the recipient address: 68UiBbsJ4PumJyVpS91VbffhKgq9p6QaLC8QCqzgLiKBX71mvCswmeViTHDsBJ3RMwsVcxBSkZ3HbjHAL9qCNxh
> Introduce string for memo: 
> Introduce dusk amount for transfer: 10 DUSK
> Introduce the gas limit for this transaction: 750000
> Introduce the gas price for this transaction: 1 LUX
   > Pay with 68UiB...qCNxh
   > Recipient = 68UiB...qCNxh
   > Amount to transfer = 10 DUSK
   > Memo = 
   > Max fee = 0.00075 DUSK
> Transaction ready. Proceed? Yes
Rusk error occurred: 500 Internal Server Error: Invalid Data InvalidData

[welf]

Account used: recovery-phrase.txt from examples.

1. Shielded account can't sync:

2. An error when I try to withdraw the stake reward to the shielded account. The note is not requested by the CLI:

Withdrawing to the public account works:

3. A GraphQL error when you request the transaction history:

[xevisalle]

For what concerns the issue with the transactions, it was finally solved by running rustup self uninstall and installing Rust again. After everthing I tested, it really seems an issue with my Rust installation / toolchain. Unless @Daksh14 you have further comments on the sync issue, I guess we could close this.