ZK HACK - Puzzle 6

Extra is not always better, it can sound bad.

Puzzle Preparation

To give you a better chance of solving this puzzle, we suggest that you look through some relevant background materials. For this particular puzzle, the BTCV bug will be key.

See puzzle details on Github

Puzzle Hints

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Molestie vel vulputate diam condimentum tristique est. Eget gravida sagittis, mi donec est. Amet turpis leo morbi enim nulla lorem sed justo. Tincidunt eu diam pellentesque nibh blandit viverra. Tincidunt pellentesque ultrices ac, sed quis purus ac. Orci adipiscing sapien aenean tincidunt rutrum. Molestie in tortor risus est.Lorem ipsum dolor sit amet, consectetur adipiscing elit. Molestie vel vulputate diam condimentum tristique est. Eget gravida sagittis, mi donec est. Amet turpis leo morbi enim nulla lorem sed justo. Tincidunt eu diam pellentesque nibh blandit viverra. Tincidunt pellentesque ultrices ac, sed quis purus ac. Orci adipiscing sapien aenean tincidunt rutrum. Molestie in tortor .

Puzzle Hints

Compare the structure of the setup to the one from the BCTV14 paper. Think about what removes the ability of the prover to interact with the verifier’s inputs. Use the extra elements of the input portion of setup to account for the difference of the expected statement.

Puzzle Winners

01

wborgeaud

Puzzle completed

Score

1000

02

niooss-ledger

Puzzle completed

Score

998.7

03

jbirnick

Puzzle completed

Score

998.3

You can view all of the scores for this puzzle in the spreadsheet here.

Puzzle Submission Guidelines

General Advice

Do not fork the public repository, as your solution will be public! instead create a private copy of it by adding another remote. Another possibility is to submit the changed files or a zip using a gist.
If you would like to submit a file in a format that gist does not support, you can use another service, but still submit a gist with a link to the other service in it. We use the gist to verify your github username.

Team submissions

If you're submitting as part of a team, the team will be regarded as a single entity and the prizes will be shared among the members of the team. A single ETH address will be required for receiving the prize on behalf of the team.

Points

1000 for the first solution, then an exponential decay to 300 until midnight UTC next Monday for each correct solution .

Eligibility

Anyone that wasn't involved in puzzle creation.

Timing

Until 23:59:59 UTC next Monday and ETH address is required to receive the prize.

Write-up submission

An award will be given to the best write-up about solving the puzzle, and what's the cryptographic issue that made the protocol broken.

Puzzle Solutions

The winner of the puzzle write up was submitted by niooss-ledger, which you can view here. Joe Bebel, the puzzle creator also wrote a puzzle write up which you can view here. There were many excellent puzzle write ups submitted, you can view them directly here:

* Solution by TrapdoorTech
* Solution by obeliskgolem