Resolve on 0x

[tmashuang]

Need to see which types of contract interactions and result in 0x fourBytePrefix and how we can mitigate the getContractMethodData() to those contracts, and/or the way we slice the tx data need adjusting

metamask-extension/ui/app/store/actions.js

Line 2191 in 7333d82

const fourBytePrefix = prefixedData.slice(0, 10)

, and/or we are setting that default tx data to 0x somewhere.

This to prevent calls to fourbyte on knownMethod['0x']

[metamaskbot]

Builds ready [e3efb19]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

Page Load Metrics (624 ± 36 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	29	100	54	26	13
		domContentLoaded	337	745	623	75	36
		load	339	747	624	75	36
		domInteractive	337	745	623	75	36

[Gudahtt]

LGTM!

I was going to suggest we add a similar guard in the one other place that getMethodDataAsync is used, but it turns out that component was unused (#9050)