a34cc5e4e9
Correctly handle "unresolvable" to/from addresses in top-level messages in the Ethereum API. Specifically: 1. Fail if we can't resolve the from address. As far as I can tell, this should be impossible (the message statically couldn't have been included in the block if the sender didn't exist). 2. If we can't resolve the "to" address to an ID, use "max uint64" as the ID (`0xff0000000000000000000000ffffffffffffffff`). This will only happen if the transaction was reverted. It'll be a little confusing, but the alternative is to (a) use an empty address (will look like a contract creation, which is definitely wrong) or (b) use a random/hashed address which will likely be more confusing as it won't be "obviously weird". |
||
|---|---|---|
| .. | ||
| client | ||
| common | ||
| full | ||
| market | ||
| net | ||
| paych | ||
| backup.go | ||
| full.go | ||
| remoteworker.go | ||
| storminer.go | ||