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
From cantina issue #45. Transcript of description:
Batcher service's can be DoSed as in proof submission pipeline computationally expensive ZK proof verification is performed before any user validation checks.
Currently in handle_submit_proof_msg in aligned-batcher/src/lib.rs, the sequence of operations are
Basic message validation (chain ID, service address, signature)
ZK proof verification (expensive) if pre-verification is enabled (which is enabled by default)
User balance/ nonce checks
This sequence allows malicious actors to:
Submit arbitrarily many proofs without having sufficient locked funds
Force the batcher to perform expensive ZK proof verification
Consume significant CPU and Memory resources at no cost
Degrade/ deny service to legitimate users
We need to move that verification to the last step before accepting a batch, after balance checks.
We may also need to use some queue to limit parallel proofs being verified to avoid unbounded memory use.
Finding a way of charging for this may also help.
The text was updated successfully, but these errors were encountered:
From cantina issue #45. Transcript of description:
We need to move that verification to the last step before accepting a batch, after balance checks.
We may also need to use some queue to limit parallel proofs being verified to avoid unbounded memory use.
Finding a way of charging for this may also help.
The text was updated successfully, but these errors were encountered: