search

zkCohort / zk_texas_holdem

GNU General Public License v3.0
3 stars 1 forks source link

The project should have a comprehensive whitepaper #5

Open arosboro opened 1 year ago

arosboro commented 1 year ago

Rough WIP here: https://docs.google.com/document/d/1G64to3v6bzVXcRWPklAC0fSzrp6NFcplkdGn9BAQP0I/edit?usp=drivesdk

arosboro commented 1 year ago

@pekasus There are some inaccurate statements about the suffle. Players remove A1, A2 during round B (Shuffle keys are A's playing keys are B's). When player 0 gets the deck and removes A1 it is still encrypted with A2. She applies B1 unique keys 52 times after removing A1. Then Bob removes A2. He applies B2 unique keys 52 times, and so on. This way layer A is progressively removed, but as it is passed it is encrypted with layer B as long as a few keys are applied the card won't be message text, it will be a different intermediary ciphertext each time. The draft makes it sound like the players take off their blindfold and they can see the message text of the shuffled deck. This is inaccurate it's closer to the lock analogy than the blindfold analogy.