From dc8b876f5a1e8478bfab19d5c457d982ba3d32f7 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Thu, 14 Dec 2023 09:17:51 +0100 Subject: [PATCH 1/2] fix typos Signed-off-by: omahs <73983677+omahs@users.noreply.github.com> --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 77827d9..cf3b01a 100644 --- a/README.md +++ b/README.md @@ -25,14 +25,14 @@ ## Build Guide -The following steps will install Aleo and Leo on your machine. This workshop is compatible on macOS, Linux, and Windows machines. +The following steps will install Aleo and Leo on your machine. This workshop is compatible with macOS, Linux, and Windows machines. ### Prerequisites This workshop requires the following prerequisites. - Install `git` with [bit.ly/start-git](https://bit.ly/start-git) -- Install `Rust`with [bit.ly/start-rust](https://bit.ly/start-rust) +- Install `Rust` with [bit.ly/start-rust](https://bit.ly/start-rust) ### Installation @@ -139,7 +139,7 @@ cd tictactoe && ./run.sh A transparent & shielded custom token in Leo. -To see an example of minting and transfering tokens, run: +To see an example of minting and transferring tokens, run: ``` cd token && ./run.sh ``` From 9518d5c328b01b916e8615419f1ab58d8212d3e9 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Thu, 14 Dec 2023 09:22:23 +0100 Subject: [PATCH 2/2] fix typos Signed-off-by: omahs <73983677+omahs@users.noreply.github.com> --- battleship/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/battleship/README.md b/battleship/README.md index 7b86dd7..3fe9d1b 100644 --- a/battleship/README.md +++ b/battleship/README.md @@ -357,7 +357,7 @@ This contains only the result of Player 1's previous fire coordinate they had se If you check Player 2's ships configuration, you'll note their entire bottom row is covered by two ships, so sample valid hits on the bottom row would be: 1u64, 2u64, 4u64, 8u64, 16u64, 32u64, 64u64, and 128u64. Since Player 1's first fire coordinate (1u64) was a hit, the `hits_and_misses` field is also 1u64. -Player 1's next move will consume this `move.record`, which will update Player 1's board with the hit-or-miss, as well as figure out the result of Player 2's fire coordinate. Now that Player 1 has some `played_tiles`, they can no longer choose an alread-played fire coordinate. For example, running `aleo run play 'board_state.record' 'move.record' 1u64` will fail, because 1u64 has already been played. +Player 1's next move will consume this `move.record`, which will update Player 1's board with the hit-or-miss, as well as figure out the result of Player 2's fire coordinate. Now that Player 1 has some `played_tiles`, they can no longer choose an already-played fire coordinate. For example, running `aleo run play 'board_state.record' 'move.record' 1u64` will fail, because 1u64 has already been played. ## 8: Player 1 Takes The 3rd Turn @@ -487,7 +487,7 @@ Play continues back and forth between Player 1 and Player 2. When one player has ## ZK Battleship Privacy -How can we ensure that the ship configurations of each player remains secret, +How can we ensure that the ship configurations of each player remain secret, while being able to trustlessly and fairly play with their opponent? By taking advantage of selective privacy powered by zero knowledge proofs on Aleo. @@ -713,7 +713,7 @@ bit count = C mod 255u64 ### Adjacency Check -Given a ship's placement on the board and its bitstring representation (horizontally or vertically), we can determine if the bits are adjacent. Follow the c_adjacency_check closure in verify.aleo. Given the ship of length 2, we know it's horizontal bitstring is 11 (3u64) and it's vertical bitstring is 100000001 (257u64). If on the board, the ship starts at the bottom right corner, its horizontal ship placement string would be: +Given a ship's placement on the board and its bitstring representation (horizontally or vertically), we can determine if the bits are adjacent. Follow the c_adjacency_check closure in verify.aleo. Given the ship of length 2, we know its horizontal bitstring is 11 (3u64) and its vertical bitstring is 100000001 (257u64). If on the board, the ship starts at the bottom right corner, its horizontal ship placement string would be: 3u64 ``` 0 0 0 0 0 0 0 0