Deprecate Archiver Service

[rauljordan]

Now that we generate states on the fly by using a cool new state management technique piloted by @terencechain, we no longer need the concept of an "archival" node nor the "archiver" service in Prysm. This is a tracking issue to deprecate such service and delete its code from our repo. Blocked until v0.11 is merged in.

Edited by @terencechain 👇

Here's the list of archival RPC end points that need work on:

• ListValidatorAssignments
• GetValidatorActiveSetChanges
• GetValidatorParticipation
• ListBeaconCommittees
• StreamIndexedAttestations

[terencechain]

This is mentioned in #4958

Should we just have one canonical tracking? or you prefer a side tracking for deprecation specifically?

[terencechain]

Working on ListValidatorAssignments

[rauljordan]

Can we close this one @terencechain

[terencechain]

No, we haven't fully deprecated the archival service yet. DB and service objects still exist

[prestonvanloon]

Is this still blocked? I think that the new state management was set to default for Onyx (alpha.10+).

[terencechain]

Blocked by testing. We should let the default mode (alpha 10+) run in the wild for a few weeks before fully deprecating archival service. There's no going back or else we'll just end up reverting work like in Topaz

[rauljordan]

Resolved