Michael Sproul

One workaround for this currently is to run supernodes. Supernodes are robust against corruption from changes in node ID. We should publicise this amongst large staking providers who are likely...

I've made a change here that I think will help: - https://github.com/sigp/lighthouse/pull/6422

Let's do it 🔥

Just noting that we currently use this (incorrectly) while processing RPC requests: https://github.com/sigp/lighthouse/blob/e5b4983d6baf85770fe4539a565d8a2dd462bc53/beacon_node/network/src/network_beacon_processor/rpc_methods.rs#L1165-L1191 We should update to use the data column custody info, or the data availability boundary as appropriate.

I'm actually torn on removing this now. I'm writing down some pros and cons to help me make my mind up ## Pros to removing - Remove cross-database transactions for...

Conclusion from our meeting today: - Keep `BlobInfo`. This will soon only be relevant for archive nodes backfilling beyond the DA period (i.e. `--complete-blob-backfill`). We might want to migrate it...

I've just re-targeted this at the `electra-alpha10` branch so we can get a conga-line going.

Looks like one of the SSE tests is failing (`get_events`)

@mask-pp The logs compress well. It's best if you can compress them and send the whole file as it is all potentially relevant Something else you could check would be...

Closing as resolved/stale. Feel free to reopen if you're still having issues