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
The current ClusterPrefixedMessagesReceivedRecord type has the implementation of Entity on it. Review the ClusterPrefixedMessagesReceivedRecord type to check that ID() method is being used and if so confirm that its ID() returns unique hash of all the content of ClusterPrefixedMessagesReceivedRecord according to encoding rlp rules.
Definition of done
Check usages of the ID() method.
All structure fields are verified to be included in the hash.
Make sure all tests work as expected.
The text was updated successfully, but these errors were encountered:
UlyanaAndrukhiv
changed the title
[Malleability A] ClusterPrefixedMessagesReceivedRecord
[Malleability] Fix ID miuse in ClusterPrefixedMessagesReceivedRecord type
Feb 11, 2025
Moved this issue to [EPIC] Refactor herocache/mempool package because ClusterPrefixedMessagesReceivedRecord is internally used by cache.RecordCache with mempool.Backend.
UlyanaAndrukhiv
changed the title
[Malleability] Fix ID miuse in ClusterPrefixedMessagesReceivedRecord type
[Malleability] Fix ID misuse in ClusterPrefixedMessagesReceivedRecord type
Feb 11, 2025
Context
The current
ClusterPrefixedMessagesReceivedRecord
type has the implementation ofEntity
on it. Review theClusterPrefixedMessagesReceivedRecord
type to check thatID()
method is being used and if so confirm that itsID()
returns unique hash of all the content ofClusterPrefixedMessagesReceivedRecord
according to encoding rlp rules.Definition of done
ID()
method.The text was updated successfully, but these errors were encountered: