Chase
Actually, yes. ``` [EROR] [08-08|16:58:39.350] RPC method debug_traceBlockByNumber crashed: interface conversion: interface {} is float64, not int64 [service.go:217 panic.go:838 runtime.go:2161 panic.go:838 vm.go:512 panic.go:838 iface.go:262 jsvm.go:80 tracer.go:135 jsvm.go:62 value.go:556 value.go:339 runtime.go:1756...
So there are like 34,000 blocks that cannot be traced and have this method handler crashed after a `null` / invalid JSON https://gist.github.com/maurodelazeri/692d04d143fc15ff06549d4c4512ed31 Rel: #4935
Wouldn't the other logs that are returned already be in the same "state" as the missing bor log? They're all old logs, they're all in the same "state"
How can I track the issue (feature request) if not via github issue?
Still an issue
Still an issue
https://chasewright.com/getting-started-with-turbo-geth-on-ubuntu/
You don't need an archive lighthouse to use archive erigon. Also: 