Live data from Hacker News

Soundness Error in BrainSTARK

aszepieniec.github.io

1–4 of 4 posts

Re: Soundness Error in BrainSTARK

#3
Unfortunately this can add some overhead to the memory table though. I wonder if there's a better solution than the one proposed here. Not that it matters for Brainfuck too much, as it's a toy language, but it would be very relevant for bigger STARK VMs.

Re: Soundness Error in BrainSTARK

#4
Worth noting is that this solution does not constrain the memory value of the last execution trace if the execution trace ends with a `>` or a `Building sound and complete STARKs are really an intricate affair! I have no doubt that we'll eventually get there though!