The prover hasn't provided a correct proof! #10

Closed
opened 2023-06-03 16:38:16 +02:00 by Benjamin_Loison · 1 comment

Reproducibility:

./verifier.py 8c6131cb2fecbb8e6468b295f44ff95ab6410e1e8726eb1ff7bc970c689f7f73 163b27578d8efd1171501bf814cc0eb5d6709d02215e292938c45a0320b9b640 '{2788, 2053, 2664, 1033, 3672, 428, 1357, 3406, 2799, 2003, 2900, 3903, 3768, 3643, 1116, 3325, 3167, 1183}'

The problem comes from merkleTreeRoot == merkleTreeLevels[-1][0] verification on verifier side.

Maybe if meta.py could give us the ratio of failure it could help us guess the issue.

Reproducibility: ```sh ./verifier.py 8c6131cb2fecbb8e6468b295f44ff95ab6410e1e8726eb1ff7bc970c689f7f73 163b27578d8efd1171501bf814cc0eb5d6709d02215e292938c45a0320b9b640 '{2788, 2053, 2664, 1033, 3672, 428, 1357, 3406, 2799, 2003, 2900, 3903, 3768, 3643, 1116, 3325, 3167, 1183}' ``` The problem comes from `merkleTreeRoot == merkleTreeLevels[-1][0]` verification on verifier side. Maybe if `meta.py` could give us the ratio of failure it could help us guess the issue.
Benjamin_Loison referenced this issue from a commit 2023-06-03 19:32:30 +02:00
Author
Owner

The issue was due to ast.literal_eval(str(indexesRequest)) not being idempotent in terms of order preservation (as set is unordered) with indexesRequest being a set.

The issue was due to `ast.literal_eval(str(indexesRequest))` not being idempotent in terms of order preservation (as `set` is unordered) with `indexesRequest` being a `set`.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Benjamin_Loison/Proof_of_Space-Time_prototype#10
No description provided.