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 Jun 6, 2023. It is now read-only.
in getting a msig transaction, if the checkHash is not set, the hash is calculated and gas charged even if the proposal hash is nil. Every use of this function sets checkHash to true, so this issue could be to remove that parameter to reduce confusion if not being planned to be used.
Previously, we'd always compute the hash but only _compare_ it if it
was specified. This simply increased the cost of messages that didn't
specify the hash for no good reason.
fixes#1364
Previously, we'd always compute the hash but only _compare_ it if it
was specified. This simply increased the cost of messages that didn't
specify the hash for no good reason.
fixes#1364
Previously, we'd always compute the hash but only _compare_ it if it
was specified. This simply increased the cost of messages that didn't
specify the hash for no good reason.
fixes#1364
Previously, we'd always compute the hash but only _compare_ it if it
was specified. This simply increased the cost of messages that didn't
specify the hash for no good reason.
fixes#1364
)
* compute the hash of the proposal iff the proposal hash is present
Previously, we'd always compute the hash but only _compare_ it if it
was specified. This simply increased the cost of messages that didn't
specify the hash for no good reason.
fixes#1364
Co-authored-by: ZenGround0 <ZenGround0@users.noreply.github.com>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
in getting a msig transaction, if the
checkHash
is not set, the hash is calculated and gas charged even if the proposal hash isnil
. Every use of this function setscheckHash
to true, so this issue could be to remove that parameter to reduce confusion if not being planned to be used.specs-actors/actors/builtin/multisig/multisig_actor.go
Line 513 in c7ea991
The text was updated successfully, but these errors were encountered: