9b4df6a4d0
We need to always use the state-tree from the tipset _after_ the message executed. If we use any other state-tree, we might not find the address we're trying to resolve. This change also has some implication for pending messages: there's no guarantee we'll be able to generate a 0x-style address for a pending native message. So, instead of trying, I've removed support for pending native messages from the Eth API. Messages from EthAccounts will still work, and native messages will still show up in blocks/traces, they just won't show up as "pending". Which should affect exactly nobody. I'm also taking this opportunity to cleanup some edge-cases: 1. Pass contexts where appropriate. 2. Remove all state access from `ethTxHashFromSignedMessage`. Part of #11355 |
||
|---|---|---|
| .. | ||
| chain.go | ||
| dummy.go | ||
| eth_event.go | ||
| eth_test.go | ||
| eth_trace.go | ||
| eth_utils.go | ||
| eth.go | ||
| gas_test.go | ||
| gas.go | ||
| mpool.go | ||
| multisig.go | ||
| raft.go | ||
| state.go | ||
| sync.go | ||
| txhashmanager.go | ||
| wallet.go | ||