lotus/node/impl
Steven Allen 9b4df6a4d0
fix: eth: use the correct state-tree when resolving addresses (#11387)
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
2023-11-17 18:20:31 +01:00
..
client Merge branch 'feat/nv21' into asr/merge-feat-nv21 2023-10-16 11:13:33 -04:00
common feat: Add node uptime rpc / output in info command 2022-10-11 10:11:09 +02:00
full fix: eth: use the correct state-tree when resolving addresses (#11387) 2023-11-17 18:20:31 +01:00
market chore: fix imports 2022-06-14 17:00:51 +02:00
net stop using go-libp2p deprecated peer.ID.Pretty 2023-09-12 13:13:34 +08:00
paych chore: fix imports 2022-06-14 17:00:51 +02:00
backup.go Plumb contexts through 2021-12-11 17:04:00 -05:00
full.go Refactor eth.go 2023-08-28 17:48:22 +00:00
remoteworker.go storage: Move extern/sector-storage to storage/sealer 2022-06-14 20:03:38 +02:00
storminer.go fix: add lk.Lock() and move the map copy to avoid miner crash 2023-11-03 15:38:20 +01:00