vshvsh

Can we pipe becon chain block roots to eth1x as well? Would be very useful for applications that depend on beacon chain, like staking pools, which are forced to use...

That looks like a building delegation mechanism in ETH2 step by step. I think it's a good direction but there might be a better approach in sketching out the whole...

Here's what happens (tried it a few times today to the same result): 1. full images `rebuild --no-cache` and volume cleaning, starting from scratch using your docker-compose files with no...

My best guess is that https://github.com/polkascan/polkascan-pre-harvester/blob/40003e2d3d2c5ca45b3e015e097851a53590da63/app/processors/converters.py#L811 remove_block happens, but https://github.com/polkascan/polkascan-pre-harvester/blob/40003e2d3d2c5ca45b3e015e097851a53590da63/app/processors/converters.py#L815 add block doesn't for some reason

Blocks that can't be added by integrity checks are processed fine when calling harvester api's process endpoint later.

I'm pretty sure this will fix the problem, reorgs were obviously the culprits. Thanks!

With `FINALIZATION_ONLY=1` it works fine, but I think the issue should stay open because without that option polkascan still fails to sync

It's likely the result of underprocessing of utility.batch e.g. https://polkascan.io/polkadot-cc1/transaction/0x83736c05aed56af76c3b1b178b764b494127f96342acc3a7713cfa31eff4db79

That's a great way to introduce key rotation for staking pools that want to reduce their reliance on custodial or semi-custodial solutions. I think that withdrawal credential compromise scenario shouldn't...

> Note that this proposal does not allow a change of validator key, so wouldn't help much in this situation. Validators are not custodians though.