Yes...the following scenarios would be applicable:
1) Sending to a previously unknown address:
Amount: 3 ETH Destination: 0x00000000000000000000000000000000 [X] Remember this address [as Edmund]
"WARNING: CONFIRM SEND <TOKEN/ETH> TO ADDRESS <ETH ADDRESS>. [PLEASE VERIFY TRANSACTION ON YOUR HARDWARE WALLET.] DESTINATION ADDRESS WILL BE SAVED IN ADDRESS BOOK AS 'EDMUND' "
Upon confirmation, the destination address would be saved as Edmund. When checking the checkbox "Remember this address", additional text shows up "as" with a field to enter the name (or alternative workflow pattern such as dialogue box).
2) Sending to an existing address in the address book:
The destination field could also accept an address book entry (auto-complete). Upon matching of an address book entry, the name is displayed, with the last transfer date and associated amount for user familiarity / verification. Perhaps a 'More Info' hyperlink next to it to also pull the transaction history from the blockchain to show the full transaction history (as annotated perhaps as well with transaction labeling as per the associated metadata labeling idea).
So it would "remember the address" and this also might help avoid a mistake copy pasting the address. You are now sending to "Luke" with a checkbox next to it. 3 Transactions already.
The address book should be encrypted as appropriately with an opt-in/or opt-out feature so that people may preserve anonymity with transactions if they so wish.
Yes...the following scenarios would be applicable:
1) Sending to a previously unknown address:
Amount: 3 ETH
Destination: 0x00000000000000000000000000000000 [X] Remember this address [as Edmund]
"WARNING: CONFIRM SEND <TOKEN/ETH> TO ADDRESS <ETH ADDRESS>. [PLEASE VERIFY TRANSACTION ON YOUR HARDWARE WALLET.] DESTINATION ADDRESS WILL BE SAVED IN ADDRESS BOOK AS 'EDMUND' "
Upon confirmation, the destination address would be saved as Edmund. When checking the checkbox "Remember this address", additional text shows up "as" with a field to enter the name (or alternative workflow pattern such as dialogue box).
2) Sending to an existing address in the address book:
Amount: 3 ETH
Destination: [Edmund] (last transfer: DD/MM/YYYY, amount: 2 ETH) (More Info)
The destination field could also accept an address book entry (auto-complete). Upon matching of an address book entry, the name is displayed, with the last transfer date and associated amount for user familiarity / verification. Perhaps a 'More Info' hyperlink next to it to also pull the transaction history from the blockchain to show the full transaction history (as annotated perhaps as well with transaction labeling as per the associated metadata labeling idea).
Attachments Open full size
So it would "remember the address" and this also might help avoid a mistake copy pasting the address. You are now sending to "Luke" with a checkbox next to it. 3 Transactions already.
Attachments Open full size
The address book should be encrypted as appropriately with an opt-in/or opt-out feature so that people may preserve anonymity with transactions if they so wish.
Attachments Open full size