When receiving a new transaction, the address book list will return to the first page. It's unclear to me what would be a good behaviour here. Due to the fact that the table is paginated, we could just stay on the same page, which would have mostly the same entries (and so on ad infinitum, so the logic wouldn't require turning to a new page after a certain point), or we could select a transaction and follow it (maybe the first transaction on the page the user selected?), or we could go to the first page as is the current behaviour, or have a button to load new entries like for the transactions list. The last one seems the most reasonable in terms of behaviour, but I don't presently see a good way to integrate it into the UI as there's not as much space as for the transactions list.
When receiving a new transaction, the address book list will return to the first page. It's unclear to me what would be a good behaviour here. Due to the fact that the table is paginated, we could just stay on the same page, which would have mostly the same entries (and so on ad infinitum, so the logic wouldn't require turning to a new page after a certain point), or we could select a transaction and follow it (maybe the first transaction on the page the user selected?), or we could go to the first page as is the current behaviour, or have a button to load new entries like for the transactions list. The last one seems the most reasonable in terms of behaviour, but I don't presently see a good way to integrate it into the UI as there's not as much space as for the transactions list.