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
..
network	Merge pull request from GHSA-c2xw-px2x-pr65	2020-10-06 15:27:02 -02:30
permissions	Update ESLint shared config to v3 (#9274)	2020-08-19 13:57:05 -02:30
transactions	Refactor background Segment usage (#9509)	2020-10-08 09:41:23 -07:00
cached-balances-test.js	Fix no-empty-function issues (#9216)	2020-08-14 09:17:02 -02:30
detect-tokens-test.js	Use Infura v3 API (#9368)	2020-09-10 13:46:00 -02:30
ens-controller-test.js	Fix import/no-extraneous-dependencies issues (#9232)	2020-08-14 17:34:56 -02:30
incoming-transactions-test.js	Use chainId for incoming transactions controller (#9583)	2020-10-30 22:28:12 -02:30
metamask-controller-test.js	Remove localhost provider type (#9551)	2020-10-12 12:05:40 -07:00
preferences-controller-test.js	Remove localhost provider type (#9551)	2020-10-12 12:05:40 -07:00
swaps-test.js	Fix swaps when initial network not Mainnet (#9745)	2020-10-28 16:17:32 -02:30
token-rates-controller.js	Fix import/order issues (#9239)	2020-08-18 16:48:25 -02:30