You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1063 there were somediscussions about potentially streamlining the data structures used to
manage attestations.
We manage attestations in two places right now:
In the Staking Extension pallet, through the use of ValidationQueue
In the Attestation pallet, through the use of PendingAttestations and AttestationRequests
We update the ValidationQueue in the Attestation pallet through the use of some
associated types, so it could make sense for us to abstract all that logic out in a
similar fashion.
It would be great it this could let us get rid of those two storage structures as well as
the Attestation pallet's on_initialize hook which is updating them based off the
entried in ValidationQueue.
The text was updated successfully, but these errors were encountered:
In #1063 there were some discussions about potentially streamlining the data structures used to
manage attestations.
We manage attestations in two places right now:
ValidationQueue
PendingAttestations
andAttestationRequests
We update the
ValidationQueue
in the Attestation pallet through the use of someassociated types, so it could make sense for us to abstract all that logic out in a
similar fashion.
It would be great it this could let us get rid of those two storage structures as well as
the Attestation pallet's
on_initialize
hook which is updating them based off theentried in
ValidationQueue
.The text was updated successfully, but these errors were encountered: