richard
richard
@danielCalbonero12345 @guybrush hi, Although `RECEIPTS_MODE_BATCH` can be used to circumvent this issue, merging this PR can maintain consistency of our code repo and the upstream. Any questions are welcome for...
request too! also I think we can add upgrade type 0x1 to type 0x2, I think is just sepcial case for consolidation requests(source pubkey==tartget pubkey), This way, users don't need...
> request too! also I think we can add upgrade type 0x1 to type 0x2, I think is just sepcial case for consolidation requests(source pubkey==tartget pubkey), This way, users don't...
@rimrakhimov Can you help review it?
@sevenzing Could you have a look?
@sevenzing @rimrakhimov ping
@metachris sir, can you take a look at this? That way I won't have to maintain my own local version
``` echo "First: $(docker logs besu-teku-beacon-1 2>&1 | grep "Loaded validator key" | head -n1)" && echo "Last: $(docker logs besu-teku-beacon-1 2>&1 | grep "Loaded validator key" | tail -n1)"...
> If key loading time is an issue, you can try converting the keystores from Scrypt (the default format from most deposit tools) to PBKDF2 format. [This tool](https://github.com/kilnfi/eth2-keystore-converter) comes from...
> @ohko4711 are you referring Scrypt or PBKDF2 encrypted keys? as user/validator, I just figured out that teku is slowly when loading a lot of keys than lighthouse/prysm, at that...