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
{{ message }}
This repository has been archived by the owner on May 29, 2024. It is now read-only.
The withdrawal_safety heuristic currently verifies that a CrossDomainHash is reflective of a standard 256 bit hexadecimal hash output. This is done by taking the Sorensen Dice coefficient to ensure dissimilarity when compared to constant values (0x0...0, 0xF...F). Currently this check happens in the heuristic directly and fails to consider for additional constant values.
Problem Solution
Add some HashVerification function into the common/mathlibrary that performs integrity checks to verify if a value is reflective of a real hash output. This can extend on the existing implementation or leverage more intelligent techniques.
The text was updated successfully, but these errors were encountered:
Problem
The
withdrawal_safety
heuristic currently verifies that aCrossDomainHash
is reflective of a standard 256 bit hexadecimal hash output. This is done by taking the Sorensen Dice coefficient to ensure dissimilarity when compared to constant values (0x0...0
,0xF...F
). Currently this check happens in the heuristic directly and fails to consider for additional constant values.Problem Solution
Add some
HashVerification
function into thecommon/math
library that performs integrity checks to verify if a value is reflective of a real hash output. This can extend on the existing implementation or leverage more intelligent techniques.The text was updated successfully, but these errors were encountered: