Transaction history entries for shielding transactions are showing incorrect amounts

[tw0po1nt]

Describe the issue

Please provide a general summary of the issue you're experiencing In Nighthawk, I autoshield my funds and expect to see a wallet event for it. I see an outgoing txn with the proper memo, but the amounts are wrong.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. Launch Nighthawk 2.0
2. Import a wallet with transparent funds or create a new wallet and send transparent funds to it
3. When the transparent funds are available to spend, swipe to the transparent balance tab in the home balance carousel.
4. Observe the "Shield now". Press it.
5. Tap the "Great!" button to confirm shielding
6. Observe that your transparent balance is now correct at 0 ZEC (or TAZ if using testnet)
7. Find the outgoing transaction in the list of recent events, or navigate to the full transaction history by tapping "View transaction history"
8. Observe the transaction details

Expected behaviour

Tell us what should happen

I expect to see the correct net value delta of the transaction at the top, as well as in a line item at the bottom.

Actual behaviour + errors

Tell us what happens instead including any noticeable error output (any messages displayed on-screen when e.g. a crash occurred)

Instead of the correct amount, I see what appears to be only the fee.

• App Version: 2.0.0
• iOS Version: iOS 17
• Device: (if applies) N/A

Any extra information that might be useful in the debugging process.

[nuttycom]

The value of the transaction you see is the net delta to the account, which is indeed just the fee. Your overall wallet balance hasn't changed by the value of the amount being shielded.

[nuttycom]

If you need to see the value of the shielded output, this is available from the transaction outputs. But I think it would be confusing to show the full shielded amount as received.

[nuttycom]

@tw0po1nt given what I've described above, is there any action that needs to be taken here, or can this be closed?

[tw0po1nt]

This can be closed. How to resolve the UX confusion can be discussed further in Discord