Mark Stacey 55bff07bbf Use chainId for incoming transactions controller (#9583) ... The incoming transactions controller now uses the `chainId` for the current network instead of the `networkId`. This ensures that custom RPC endpoints for the built-in supported networks do correctly receive incoming transactions. As part of this change, the incoming transactions controller will also cease keeping track of the "last block fetched" for networks that are not supported. This piece of state never really represented the last block fetched, as _no_ blocks were fetched for any such networks. It been removed.		2020-10-30 22:28:12 -02:30
..
data	Use chainId values for the address book (#9565)	2020-10-12 16:35:55 -07:00
e2e	Robustify waiting logic in e2e test (#9704)	2020-10-23 16:24:20 -07:00
lib	Add unit tests for incoming transaction block events (#9755)	2020-10-30 11:47:36 -02:30
stub	Fix fetching of swap quotes when initial network was testnet (#9726)	2020-10-27 13:22:21 -02:30
unit	Use chainId for incoming transactions controller (#9583)	2020-10-30 22:28:12 -02:30
unit-global	Fix no-empty-function issues (#9216)	2020-08-14 09:17:02 -02:30
env.js
helper.js	Update @metamask/eslint-config to v4.1.0 (#9663)	2020-10-21 14:01:03 -02:30
setup.js