Update initial earliest_exit_epoch calculation

[hangleang]

reference spec change: ethereum/consensus-specs#4001

[hangleang]

Hi @Tumas, this spec is already implemented in devnet-5 branch, just want to know what do you think about this alter aproach

as context in devnet-5 branch:

grandine/helper_functions/src/fork.rs

Lines 549 to 561 in bfdaff2

	let mut earliest_exit_epoch = misc::compute_activation_exit_epoch::<P>(epoch);
	for exit_epoch in validators
	.into_iter()
	.map(|validator| validator.exit_epoch)
	.filter(|exit_epoch| *exit_epoch != FAR_FUTURE_EPOCH)
	{
	if exit_epoch > earliest_exit_epoch {
	earliest_exit_epoch = exit_epoch;
	}
	}
	earliest_exit_epoch += 1;

[Tumas]

Looks good, can you change the target to devnet5?

[hangleang]

I guess I have to change the base branch since a few commits from develop come along as well

[Tumas]

I've rebased devnet5 on develop, so now only the code conflicts are left.

[hangleang]

all good now

[Tumas]

It now shows 10 commits with this merge request, can you squash all your changes into 1 commit?

[hangleang]

sorry for took much time on fixing my messy commits history, done squashing those commits into one

[sauliusgrigaitis]

Thanks @hangleang , if you would like to work on Pectra then the best way would be to do Kurtosis interop with other clients (the config is in Ethereum R&D discord #interop chat) and debug the issues.

[hangleang]

Yes, but I will prioritize PeerDAS work since the implementation is not stable yet. If I still have some time left, I will pick up some easy tasks or quick-fix issues to work on.

[sauliusgrigaitis]

@hangleang sure, but PeerDAS is a bit stalled since everyone is focusing on Pectra.

[hangleang]

yeah, once I'm done with the rebase and switch to custody groups, and feel confident enough if the next devnet launch is announced, grandine is ready to go