Aaron Cook

I've looked into this and also [onboard's code](https://github.com/blocknative/onboard/blob/6e7cbb2fa5481a93f6e018bd0001c9bdf11790a6/src/modules/select/wallets/providerEngine.ts#L23). It is is the [default polling interval](https://docs.blocknative.com/onboard#blockpollinginterval-optional-default-4000). I do not see any need to change this if we have no had any...

After researching, this is a Chrome related warning. I've looked through our codebase (and that of onboard/Trezor) and it seems as though we are the only iframe users. This is...

Does the timeline take into account the adjustments required on backend and allowance of transaction proposal by delegates?

> Only frontend work as we agreed in the meeting earlier. IIRC We need to adjust the proposal logic though if we want to allow delegates to draft transactions or...

Adding to this, when unbookmarking an App, it regenerates all 'top' Apps. I think they should only regenerate on page load. What are your thoughts? (This recording was taken on...

For reference: this is a default error thrown by the `promiEvent`. It is unrelated to the pending watcher.

> @iamacook shouldn't this be tackled on the backend? Ideally, yes, but it is not on their list of things to do as it would have an [adverse effect on...

We no longer include "Contract Interaction" in web-core. As such, I'm closing this.

If I understand @mikheevm, it sounds like an error notification was shown to the user. It's strange that the transaction location didn't change if that was the previous behaviour. `saveTxToHistory()`...

Odd that it didn't show. I guess this ticket will also require looking into the error notifications as well then. Do you have details of the transaction in question?