• 56!@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    7 months ago

    Step 3 is where the issue occurs. The last party to submit their value has control over the output. Any complex calculations can easily be passed off as network lag. One solution I can think of is to pass the values round in a circle, one by one. This would require each party to share their value before they have seen all other values. At the end each party would share their calculated values to verify they match. Probably other solutions as well.

    • vzq
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      3 months ago

      deleted by creator

      • HappyRedditRefugee@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        Amazing solution, didn’t arrive to that one, I was thinking just making a timing constraint to reveal the number that would make the precaculation practically imposible, but the commitment schmeme is waaaay more elegant.