10000 Double spending threat if no range check is done on public inputs in verifier · Issue #38 · clearmatics/zeth · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Double spending threat if no range check is done on public inputs in verifier #38
New issue
New issue
Closed
Closed
Double spending threat if no range check is done on public inputs in verifier#38
Assignees
AntoineRondelet
Labels
solidityTask related to the Solidity part of the code basevulnerability
@AntoineRondelet

Description

@AntoineRondelet
AntoineRondelet
opened on Aug 5, 2019

We need to make sure that we constrain the public inputs to be <p in the verifier contract.
See: semaphore-protocol/semaphore#16

Metadata

Metadata

Assignees

Labels

solidityTask related to the Solidity part of the code basevulnerability

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    0