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 was archived by the owner on Jun 11, 2024. It is now read-only.
There should be limit on number of hash computation so that memory and cpu usage is bounded.
This RPC endpoints should be only enabled per whitelist with this issue. Therefore, this endpoint should be only called from the node operator by default.
Actual behavior
With the very high number of count for the setHashOnion like below.
Expected behavior
There should be limit on number of hash computation so that
memory
andcpu
usage is bounded.This RPC endpoints should be only enabled per whitelist with this issue. Therefore, this endpoint should be only called from the node operator by default.
Actual behavior
With the very high number of count for the
setHashOnion
like below.Steps to reproduce
Call RPC endpoint with
Which version(s) does this affect? (Environment, OS, etc...)
6.0.0-beta.1
The text was updated successfully, but these errors were encountered: