Transaction history: "Received" and "Pending confirmation" can be potentially confusing

[weilu]

From a support ticket: "Transaction says received but still pending confirmation." @jenbennings @haustraliaer Do you notice the ambiguity? Is there something we can do to disambiguate it?

[jenbennings]

How about we change it to Incoming whilst the transaction unconfirmed?

I'm not entirely happy with how we currently deal with incoming/outgoing transactions (address for outgoing, word for incoming). I understand we did this in an effort to discourage people treating incoming transactions as static wallet addresses (when they might not be), however it does lead me to question whether it would be better to simply use words for all items in the transaction list (similar to Hive OS X). Right now I find the disconnect between 'Received' and the truncated wallet address (as part of a list of transactions) quite jarring.

Since we already offer more information as part of the transaction details modal, unless I'm missing something, I don't see a compelling reason to keep it.

Instead, I propose we use:

• Incoming (unconfirmed received transaction)
• Received (confirmed received transaction)
• Outgoing (unconfirmed sent transaction)
• Sent (confirmed sent transaction)

Thoughts?

[weilu]

+1 for dropping the destination address. As for the wording, we already have "pending confirmation" and "confirmed" under the amount to differentiate the unconfirmed/confirmed transactions. Can we do with just "Incoming" and "Outgoing" for the words on the left?

[haustraliaer]

I think the words should change - as ben proposed. Incoming and Outgoing infer that something is still happening.

[weilu]

What about ⤋ and ⤊? Saves all the trouble to translate :P

[dabura667]

+1 for dropping sending Addresses

+1 for Incoming Outgoing (when not in block) Received Sent (when in most recent block.)

I'll give two suggestions with varying difficulty for the "Pending" issue:

1. Remove it completely, and only show a special message there in the case of an orphan. (aka a user viewed it as Received, then it got orphaned and they viewed the same transaction. while it was still not in a block) Though this would be super difficult, as it would be hard to set up a flag for "was in orphan" etc.
2. Change it to "Low confirmation count" with an info window pop up that says "Transactions with low confirmation counts have a slim chance of becoming unconfirmed. If a transaction becomes unconfirmed, it will most likely be confirmed again within the next 10 minutes." or something along those lines.

[weilu]

Actually, maybe it'd be more informative if we display the address that a transaction is received with instead of the word "Received" or "Incoming", as currently when we rotate to the next receiving address, previous addresses can only be looked up with transaction IDs on block explorers like blockchain.info

[dabura667]

I would say to put those into a "Used Addresses" section or put them in the transaction details popup if they are wanted.

However, personally I think continuing to show the used addresses to the user is only for more technical people. I would assume this UI is geared more towards the average joe... so I would say no to showing the receiving address at all.

[mattatgit]

@w i think the incoming/received outgoing/sent labels above are good & we should use them.