Allow configuration of transaction card expiry time

[jmhickman]

This is a shot of my local Ganache node, and two completed transactions. I don't know why Frame would continue to make that eth call once the UI has updated and shown the transactions to be complete.

Possibly related, the arrows that progress from left to right along the top of the transaction card are frozen in place.

[jmhickman]

The cards will continue to stack up basically forever

Frame crashed shortly after this screen was taken. Nothing interesting in the log for the crash, just some complaints that the ganache endpoint doesn't support subscriptions.

[jmhickman]

I was able to get to the bottom of this stacking transactions behavior.

If the chain Frame is connected to doesn't continuously mine blocks, (as dev chains are often set to) then these cards will never disappear.

However, if you run geth with the --dev.period option to simulate continuous block production, Frame behaves normally.

So the time the card is displayed seems to be linked to block production time. My guess is that the repeated eth_getTransactionReceipt is how the blocktime() is being fetched?

I feel like this shouldn't be tied to the chain in any way, but should just be an unrelated timespan. This would enable the option to allow the user to specify how long they'd like the cards to stick around.