Willian Mitsuda

Tx on goerli showing incorrectly as flashbots

2

See tx: 0xe50d224429fe835e21cffb768960a485a99e61af11c8eff456fbb07cec00e3bd on goerli

Currently this method handles only yes/no cases of addresses having a contract deployed. In order to properly handle pruned nodes, we need to implement the "no info" case. Issue raised...

See: https://twitter.com/totlsota/status/1512743655169310726

Try http://localhost:3000/block/14453498/txs?p=3 on sepolia for example.

See tx: 0xec15f329533439206ca776445e15ebc4357722fed842c113893232bce92af724

See: https://discord.com/channels/687972960811745322/860269083656323082/889948804806234234

v2022.08.02 Can't do a clean shutdown if you Ctrl+C while it is running stage 6, had to force interrupt to exit it: ``` INFO[08-17|16:53:01.981] [6/16 Execution] Executed blocks number=15356193 blk/s=8.6...

"exited with code 137" at bodies stage

8

v2022.07.02, I'm trying to sync goerli, it keeps being killed at ~same stage/block, it seems because out of memory, but I gave 16GB for the entire docker process. I'll try...

Node stuck on sepolia on headers download

5

v2022.06.02 I'm attaching the debug logs. [sepolia-log-debug.txt](https://github.com/ledgerwatch/erigon/files/8911791/sepolia-log-debug.txt)

Erigon repeatedly crashing when running along prysm

3

v2022.08.03 I really don't know if it's a random issue, but in one of my runs, starting a docker compose setup which starts erigon and prysm simultaneously led to erigon...