Add vote management

Before you begin

• You have an internet connection and a web browser installed on your local computer.
• You have a code editor, such as Visual Studio Code, access to an interactive terminal shell, and are generally familiar with using command-line programs.
• You have cloned the voting-dapp repository to create your project directory as described in Prepare your workspace.
• You have the development network running in a Docker container as described in Start a local blockchain.
• You are connected to the development network using your local host IP address and port number 8080.
• You have created and funded an administrative account as described in Add an administrator account.
• You have created a principal namespace on the development network as described in Define a namespace.
• You have defined the keyset that controls your namespace using the administrative account as described in Define keysets.
• You have created an election Pact module and deployed it as described in Write a smart contract and updated its functionality as described in Nominate candidates.

Increment votes for a candidate

Organize your REPL files

1. Open the election-dapp/pact folder in the code editor on your computer.

2. Rename election.repl to candidates.repl.

3. Create a new setup.repl file in the pact folder.

4. Move the code before (begin-tx "Load election module") from the candidates.repl into the setup.repl file.

5. Create a new voting.repl file in the pact folder and add the following as the first line in the file:

   (load "setup.repl")

   (load "setup.repl")

6. Open the candidates.repl file and and add the following as the first line in the file:

   (load "setup.repl")

   (load "setup.repl")

7. Verify tests in the candidates.repl file still pass by running the following command:

   pact candidates.repl --trace

   pact candidates.repl --trace

8. Verify that voting.repl loads successfully by running the following command:

   pact voting.repl --trace

   pact voting.repl --trace

Prepare a test for incrementing votes

1. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

2. Add transactions to load the election Pact module and to add a candidate to the candidates table:

   (begin-tx "Load election module")  (load "election.pact")(commit-tx) (begin-tx "Add a candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (add-candidate { "key": "1", "name": "Candidate A" })(commit-tx)

   (begin-tx "Load election module")  (load "election.pact")(commit-tx) (begin-tx "Add a candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (add-candidate { "key": "1", "name": "Candidate A" })(commit-tx)

   Remember to replace the namespace with your own principal namespace.

3. Add the following lines of code to test a voting transaction:

   (begin-tx "Voting for a candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect    "Candidate A has 0 votes"    0    (at 'votes (at 0 (list-candidates)))  )  (vote "1")  (expect    "Candidate A has 1 vote"    1    (at 'votes (at 0 (list-candidates)))  )(commit-tx)

   (begin-tx "Voting for a candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect    "Candidate A has 0 votes"    0    (at 'votes (at 0 (list-candidates)))  )  (vote "1")  (expect    "Candidate A has 1 vote"    1    (at 'votes (at 0 (list-candidates)))  )(commit-tx)

   This code:

   • Verifies that the candidate is initialized with zero votes.
   • Calls the vote function with the key value (1) of the candidate as the only argument.
   • Asserts that the candidate has one vote.

   If you were to execute the transaction, the test would fail because the vote function doesn't exist yet in the election module and you would see output similar to the following:

   voting.repl:18:5:Error: Cannot resolve voteLoad failed

   voting.repl:18:5:Error: Cannot resolve voteLoad failed

4. Open the election-dapp/pact/election.pact file in your code editor.

5. Define the vote function after the add-candidate function with the following lines of code:

   (defun vote (candidateKey:string)  (with-read candidates candidateKey    { "name" := name, "votes" := numberOfVotes }    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })  ))

   (defun vote (candidateKey:string)  (with-read candidates candidateKey    { "name" := name, "votes" := numberOfVotes }    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })  ))

   In this code, the vote function takes the candidateKey parameter with a type of string:

   • The candidateKey value specifies the key for the row in the candidates table to read using the built-in with-read Pact function.
   • The database column named "votes" is assigned a value from the numberOfVotes variable.

   The vote function then calls the built-in update Pact function with three arguments to specify:

   • The table to update (candidates).
   • The key for the row to update (candidateKey).
   • An object with the column names to update and the new value for the respective columns. In this case, the vote function only updates the votes column. The new value is the current number of votes that was obtained from with-read and stored in the numberOfVotes variable incremented by one ((+ numberOfVotes 1)).

6. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see the transaction succeeds with output similar to the following:

   voting.repl:13:5:Trace: Expect: success: Candidate A has 0 votesvoting.repl:18:5:Trace: Write succeededvoting.repl:19:5:Trace: Expect: success: Candidate A has 1 votevoting.repl:24:3:Trace: Commit Tx 4: Voting for a candidateLoad successful

   voting.repl:13:5:Trace: Expect: success: Candidate A has 0 votesvoting.repl:18:5:Trace: Write succeededvoting.repl:19:5:Trace: Expect: success: Candidate A has 1 votevoting.repl:24:3:Trace: Commit Tx 4: Voting for a candidateLoad successful

Prepare a test for voting on an invalid candidate

1. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

2. Add the following transaction before the Voting for a candidate transaction:

   (begin-tx "Voting for a non-existing candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote for a non-existing candidate"    (vote "20")  )(commit-tx)

   (begin-tx "Voting for a non-existing candidate")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote for a non-existing candidate"    (vote "20")  )(commit-tx)

   Remember to replace the namespace with your own principal namespace.

3. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction succeeds with output similar to the following:

   voting.repl:11:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:12:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:13:5:Trace: Expect failure: success: Cannot vote for a non-existing candidatevoting.repl:17:0:Trace: Commit Tx 4: Voting for a non-existing candidate

   voting.repl:11:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:12:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:13:5:Trace: Expect failure: success: Cannot vote for a non-existing candidatevoting.repl:17:0:Trace: Commit Tx 4: Voting for a non-existing candidate

   The test returns the expected result—failure—because the call to with-read fails for the candidateKey value of "20". The failure prevents the execution of the update function.

   As you add checks to the vote function, you should return more specific error messages, so that each check provides information about why it failed to the caller of the function.

4. Update the invalid candidate transaction to specify "Candidate does not exist" as the expected error message:

   (begin-tx "Voting for a non-existing candidate")(use n_14912521e87a6d387157d526b281bde8422371d1.election)(expect-failure "Cannot vote for a non-existing candidate" "Candidate does not exist" (vote "X"))(commit-tx)

   (begin-tx "Voting for a non-existing candidate")(use n_14912521e87a6d387157d526b281bde8422371d1.election)(expect-failure "Cannot vote for a non-existing candidate" "Candidate does not exist" (vote "X"))(commit-tx)

   In this code:

   • This first argument of expect-failure is the name of the test.
   • The second argument is the expected output of the function call.
   • The third argument is the actual function call.

5. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction fails with output similar to the following:

   voting.repl:11:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:12:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:13:5:Trace: FAILURE: Cannot vote for a non-existing candidate: expected error message to contain 'Candidate does not exist', got '(with-read candidates candidat...: Failure: Tx Failed: with-read: row not found: X'voting.repl:18:0:Trace: Commit Tx 4: Voting for a non-existing candidate

   voting.repl:11:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:12:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:13:5:Trace: FAILURE: Cannot vote for a non-existing candidate: expected error message to contain 'Candidate does not exist', got '(with-read candidates candidat...: Failure: Tx Failed: with-read: row not found: X'voting.repl:18:0:Trace: Commit Tx 4: Voting for a non-existing candidate

   Because the error message doesn't contain the expected output of Candidate does not exist that you specified in the previous step, the with-read function returns a default error message. If you want to provide a more specific error message, you can use the built-in with-default-read Pact function. The with-default-read function enables you to return a default object with default values or a specific error message if a specific condition is detected. In this example, you can use the with-default-read function to set the default values for the name ("") and votes (0) columns.

6. Open the election-dapp/pact/election.pact file in your code editor.

7. Update the vote function to use the with-default-read function:

   (defun vote (candidateKey:string)  (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })  ))

   (defun vote (candidateKey:string)  (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })  ))

   With this code, a successful read operation assigns the value of the "name" column to a name variable and the value of the "votes" column to the numberOfVotes variable. The function also checks that the candidate name associated with the candidateKey is not an empty string, and returns a specific error if it is.

8. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction succeeds with output similar to the following:

   voting.repl:12:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:13:2:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:14:2:Trace: Expect failure: success: Cannot vote for a non-existing candidatevoting.repl:19:0:Trace: Commit Tx 4: Voting for a non-existing candidate...Load successful

   voting.repl:12:0:Trace: Begin Tx 4: Voting for a non-existing candidatevoting.repl:13:2:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:14:2:Trace: Expect failure: success: Cannot vote for a non-existing candidatevoting.repl:19:0:Trace: Commit Tx 4: Voting for a non-existing candidate...Load successful

Prevent double votes

Define votes schema and table

1. Open the election-dapp/pact/election.pact file in your code editor.

2. Add the schema for the votes database table inside of the election module definition after the definition of the candidates schema and table with the following lines of code:

     (defschema votes-schema    candidateKey:string  )   (deftable votes:{votes-schema})

     (defschema votes-schema    candidateKey:string  )   (deftable votes:{votes-schema})

3. Create the table outside of the election module by adding the following lines of code at the end of ./pact/election.pact, after the election module definition and the init-candidates code snippet:

   (if (read-msg "init-votes")  [(create-table votes)]  [])

   (if (read-msg "init-votes")  [(create-table votes)]  [])

   With this code, read-msg reads the init-votes field from the transaction data. If you set this field to true in your module deployment transaction, the statement between the first square brackets is executed. This statement creates the votes table based on its schema definition inside the module when you load the module into the Pact REPL or upgrade the module on the blockchain.

4. Open the election-dapp/pact/setup.repl file in your code editor.

5. Add , 'init-votes: true to the env-data so that this data is loaded in the Pact REPL environment when you load the election module and the votes table is created:

   (env-data  { 'admin-keyset:      { 'keys : [ "5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" ]      , 'pred : 'keys-all      }  , 'init-candidates: true  , 'init-votes: true  })

   (env-data  { 'admin-keyset:      { 'keys : [ "5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" ]      , 'pred : 'keys-all      }  , 'init-candidates: true  , 'init-votes: true  })

6. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction succeeds with TableCreated twice in the output similar to the following:

   election.pact:48:0:Trace: ["TableCreated"]election.pact:53:0:Trace: ["TableCreated"]

   election.pact:48:0:Trace: ["TableCreated"]election.pact:53:0:Trace: ["TableCreated"]

Test the votes table

1. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

2. Add the following transaction to assert that it is not possible to cast more than one vote:

   (begin-tx "Double vote")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote more than once"    "Multiple voting not allowed"    (vote "1")  )(commit-tx)

   (begin-tx "Double vote")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote more than once"    "Multiple voting not allowed"    (vote "1")  )(commit-tx)

   Remember to replace the namespace with your own principal namespace.

3. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction fails with output similar to the following:

   voting.repl:37:5:Trace: FAILURE: Cannot vote more than once: expected failure, got result = "Write succeeded"voting.repl:42:3:Trace: Commit Tx 6: Double votevoting.repl:37:5:ExecError: FAILURE: Cannot vote more than once: expected failure, got result = "Write succeeded"Load failed

   voting.repl:37:5:Trace: FAILURE: Cannot vote more than once: expected failure, got result = "Write succeeded"voting.repl:42:3:Trace: Commit Tx 6: Double votevoting.repl:37:5:ExecError: FAILURE: Cannot vote more than once: expected failure, got result = "Write succeeded"Load failed

   Remember that all transactions in voting.repl are signed with the admin-keyset you defined for the REPL environment in the setup.repl file. Your administrative account can cast more than one vote on Candidate A, which makes the election unfair.

   To fix this issue, you'll need to update the vote function in the election module.

4. Open the election-dapp/pact/election.pact file in your code editor.

5. Update the vote function to include the account name and prevent the same account from voting more than once:

   (defun vote (account:string candidateKey:string)  (let ((double-vote (account-voted account)))    (enforce (= double-vote false) "Multiple voting not allowed"))   (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })    (insert votes account { "candidateKey": candidateKey })  ))

   (defun vote (account:string candidateKey:string)  (let ((double-vote (account-voted account)))    (enforce (= double-vote false) "Multiple voting not allowed"))   (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (update candidates candidateKey { "votes": (+ numberOfVotes 1) })    (insert votes account { "candidateKey": candidateKey })  ))

   This code:

   • Adds the account of the voter as the first parameter of the vote function.
   • Stores the result from a new account-voted function in the double-vote variable and uses that value to prevent an account from voting more than once.
   • Enforces that no row in the votes table is keyed with the account name using the with-default-read pattern that you used to prevent voting on a non-existent candidate.
   • Inserts a new row into the votes table with the account name as the key and the candidate key as the value for the candidateKey column every time the vote function is called.

6. Add the account-voted function to check if an account has already voted:

   (defun account-voted:bool (account:string)  (with-default-read votes account    { "candidateKey": "" }    { "candidateKey" := candidateKey }    (> (length candidateKey) 0)  ))

   (defun account-voted:bool (account:string)  (with-default-read votes account    { "candidateKey": "" }    { "candidateKey" := candidateKey }    (> (length candidateKey) 0)  ))

   The frontend of the election application can then use the result from the account-voted function to determine if Vote Now should be enabled.

7. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

8. Update all calls to the vote function to pass your administrative account name as the first argument.

   For example, update the vote function in the Double vote transaction:

   (begin-tx "Double vote")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote more than once"    "Multiple voting not allowed"    (vote "k:5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" "1")  )(commit-tx)

   (begin-tx "Double vote")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Cannot vote more than once"    "Multiple voting not allowed"    (vote "k:5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" "1")  )(commit-tx)

9. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction succeeds with output similar to the following:

   voting.repl:35:3:Trace: Begin Tx 6: Double votevoting.repl:36:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:37:5:Trace: Expect failure: success: Cannot vote more than oncevoting.repl:42:3:Trace: Commit Tx 6: Double voteLoad successful

   voting.repl:35:3:Trace: Begin Tx 6: Double votevoting.repl:36:5:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:37:5:Trace: Expect failure: success: Cannot vote more than oncevoting.repl:42:3:Trace: Commit Tx 6: Double voteLoad successful

   With these changes, the same account can't call the vote function more than once.

Prevent voting on behalf of other accounts

1. Open the election-dapp/pact/setup.repl file in the code editor on your computer.

2. Add a voter-keyset to env-data so that this data is loaded in the Pact REPL environment when you load the election module:

   , 'voter-keyset: { "keys": ["voter"], "pred": "keys-all" }

   , 'voter-keyset: { "keys": ["voter"], "pred": "keys-all" }

3. Load the coin module and the interfaces it implements with the following lines of code in the setup.repl:

   (begin-tx "Set up coin")  (load "root/fungible-v2.pact")  (load "root/fungible-xchain-v1.pact")  (load "root/coin-v5.pact")   (create-table coin.coin-table)  (create-table coin.allocation-table)   (coin.create-account "voter" (read-keyset "voter-keyset"))  (coin.create-account "k:5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" (read-keyset "admin-keyset"))(commit-tx)

   (begin-tx "Set up coin")  (load "root/fungible-v2.pact")  (load "root/fungible-xchain-v1.pact")  (load "root/coin-v5.pact")   (create-table coin.coin-table)  (create-table coin.allocation-table)   (coin.create-account "voter" (read-keyset "voter-keyset"))  (coin.create-account "k:5ec41b89d323398a609ffd54581f2bd6afc706858063e8f3e8bc76dc5c35e2c0" (read-keyset "admin-keyset"))(commit-tx)

   This code:

   • Creates the coin.coin-table and coin.allocation-table required to create the voter account.
   • Creates the voter account and your administrative account in the coin module database.

   Remember to replace the administrative account name with your own account name.

4. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

5. Add a transaction at the end of the file to cast a vote on behalf of the voter account signed by the admin-keyset.

   (begin-tx "Vote on behalf of another account")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Voting on behalf of another account should not be allowed"    "Keyset failure (keys-all): [voter]"    (vote "voter" "1")  )(commit-tx)

   (begin-tx "Vote on behalf of another account")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (expect-failure    "Voting on behalf of another account should not be allowed"    "Keyset failure (keys-all): [voter]"    (vote "voter" "1")  )(commit-tx)

   Remember to replace the namespace with your own principal namespace.

6. Execute the transaction using the pact command-line program:

   pact voting.repl --trace

   pact voting.repl --trace

   You should see that the transaction fails with output similar to the following:

   voting.repl:51:0:Trace: Commit Tx 8: Vote on behalf of another accountvoting.repl:46:2:ExecError: FAILURE: Voting on behalf of another account should not be allowed: expected failure, got result = "Write succeeded"Load failed

   voting.repl:51:0:Trace: Commit Tx 8: Vote on behalf of another accountvoting.repl:46:2:ExecError: FAILURE: Voting on behalf of another account should not be allowed: expected failure, got result = "Write succeeded"Load failed

   The test failed because the voter account name doesn't exist in the votes table keys and the candidate exists, so the number of votes for the candidate is incremented. You need to make sure that the signer of the transaction owns the account passed to the vote function.

7. Open the election-dapp/pact/election.pact file in the code editor on your computer.

8. Define the ACCOUNT-OWNER capability to enforce the guard of the account passed to the vote function:

   (use coin [ details ]) (defcap ACCOUNT-OWNER (account:string)    (enforce-guard (at 'guard (coin.details account))))

   (use coin [ details ]) (defcap ACCOUNT-OWNER (account:string)    (enforce-guard (at 'guard (coin.details account))))

   This code uses the coin.details function to get the guard for an account by account name. The details function of the coin module must be imported into the election module to be able to use it. In this case, voter-keyset is the guard for the account. By enforcing this guard, you can ensure that the keyset used to sign the vote transaction belongs to the account name passed to the function.

9. Apply the capability by wrapping the update and insert statements in the vote function inside a with-capability statement as follows:

   (defun vote (account:string candidateKey:string)  (let ((double-vote (account-voted account)))    (enforce (= double-vote false) "Multiple voting not allowed"))   (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (with-capability (ACCOUNT-OWNER account)      (update candidates candidateKey { "votes": (+ numberOfVotes 1) })      (insert votes account { "candidateKey": candidateKey })    )  ))

   (defun vote (account:string candidateKey:string)  (let ((double-vote (account-voted account)))    (enforce (= double-vote false) "Multiple voting not allowed"))   (with-default-read candidates candidateKey    { "name": "", "votes": 0 }    { "name" := name, "votes" := numberOfVotes }    (enforce (> (length name) 0) "Candidate does not exist")    (with-capability (ACCOUNT-OWNER account)      (update candidates candidateKey { "votes": (+ numberOfVotes 1) })      (insert votes account { "candidateKey": candidateKey })    )  ))

10. Execute the transaction using the pact command-line program:

    pact voting.repl --trace

    pact voting.repl --trace

    You should see that the transaction succeeds with output similar to the following:

    voting.repl:44:3:Trace: Begin Tx 8: Vote on behalf of another accountvoting.repl:45:2:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:46:2:Trace: Expect failure: success: Voting on behalf of another account should not be allowedvoting.repl:51:0:Trace: Commit Tx 8: Vote on behalf of another accountLoad successful

    voting.repl:44:3:Trace: Begin Tx 8: Vote on behalf of another accountvoting.repl:45:2:Trace: Using n_14912521e87a6d387157d526b281bde8422371d1.electionvoting.repl:46:2:Trace: Expect failure: success: Voting on behalf of another account should not be allowedvoting.repl:51:0:Trace: Commit Tx 8: Vote on behalf of another accountLoad successful

    With these changes, the administrative account can't vote on behalf of another account.

Verify voting on one's own behalf

1. Open the election-dapp/pact/voting.repl file in the code editor on your computer.

2. Add a transaction to verify that the voter account can vote on its own behalf, leading to an increase of the number of votes on Candidate A to 2:

   (env-sigs  [{ 'key  : "voter"   , 'caps : []  }]) (begin-tx "Vote as voter")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (vote "voter" "1")  (expect    "Candidate A has 2 votes"    2    (at 'votes (at 0 (list-candidates)))  )(commit-tx)

   (env-sigs  [{ 'key  : "voter"   , 'caps : []  }]) (begin-tx "Vote as voter")  (use n_14912521e87a6d387157d526b281bde8422371d1.election)  (vote "voter" "1")  (expect    "Candidate A has 2 votes"    2    (at 'votes (at 0 (list-candidates)))  )(commit-tx)

   Remember to replace the namespace with your own principal namespace.

3. Execute the transaction using the pact command-line program:

   pact voting.repl -t

   pact voting.repl -t

   You should see that the transaction succeeds with output similar to the following:

   voting.repl:62:4:Trace: Expect: success: Candidate A has 2 votesvoting.repl:67:2:Trace: Commit Tx 9: Vote as voterLoad successful

   voting.repl:62:4:Trace: Expect: success: Candidate A has 2 votesvoting.repl:67:2:Trace: Commit Tx 9: Vote as voterLoad successful

Update the development network

1. Verify the development network is currently running on your local computer.

2. Open and unlock the Chainweaver desktop or web application and verify that:

   • You're connected to development network (devnet) from the network list.
   • Your administrative account name with the k: prefix exists on chain 1.
   • Your administrative account name is funded with KDA on chain 1.

   You're going to use Chainweaver to sign the transaction that updates the election module.

3. Open the election-dapp/snippets folder in a terminal shell on your computer.

4. Deploy your election module on the development network by running a command similar to the following with your administrative account name:

   npm run deploy-module:devnet -- k:<your-public-key> upgrade init-votes

   npm run deploy-module:devnet -- k:<your-public-key> upgrade init-votes

   Remember that k:<your-public-key> is the default account name for the administrative account that you funded in Add an administrator account. You can copy this account name from Chainweaver when viewing the account watch list.

   In addition to the account name and upgrade, you must include init-votes in the command to add {"init-votes": true} to the transaction data. This field is required to allow you to execute the (create-table votes) statement from your election module.

5. Click Sign All in Chainweaver to sign the request.

   After you click Sign All, the transaction is executed and the results are displayed in your terminal shell. For example, you should see output similar to the following:

   { status: 'success', data: [ 'TableCreated' ] }

   { status: 'success', data: [ 'TableCreated' ] }

6. Verify your contract changes in the Chainweaver Module Explorer by refreshing the list of Deployed Contracts, then clicking View for the election module.

   After you click View, you should see the updated list of functions and capabilities. If you click Open, you can view the module code in the editor panel and verify that the election module deployed on the local development network is what you expect.

Update the frontend

1. Open election-dapp/frontend/src/repositories/candidate/DevnetVoteRepository.ts in your code editor.

2. Replace the value of the NAMESPACE constant with your own principal namespace.

   const NAMESPACE = 'n_14912521e87a6d387157d526b281bde8422371d1';

   const NAMESPACE = 'n_14912521e87a6d387157d526b281bde8422371d1';

3. Review the hasAccountVoted function:

   const hasAccountVoted = async (account: string): Promise<boolean> => {  const transaction = Pact.builder    // @ts-ignore    .execution(Pact.modules[`${NAMESPACE}.election`]['account-voted'](account))    .setMeta({ chainId: CHAIN_ID })    .setNetworkId(NETWORK_ID)    .createTransaction();  const { result } = await client.dirtyRead(transaction);   if (result.status === 'success') {    return result.data.valueOf() as boolean;  } else {    console.log(result.error);    return false;  }};

   const hasAccountVoted = async (account: string): Promise<boolean> => {  const transaction = Pact.builder    // @ts-ignore    .execution(Pact.modules[`${NAMESPACE}.election`]['account-voted'](account))    .setMeta({ chainId: CHAIN_ID })    .setNetworkId(NETWORK_ID)    .createTransaction();  const { result } = await client.dirtyRead(transaction);   if (result.status === 'success') {    return result.data.valueOf() as boolean;  } else {    console.log(result.error);    return false;  }};

4. Remove the @ts-ignore comment from the function and notice the resulting errors. To fix the errors, you must generate types for your Pact module that can be picked up by @kadena/client.

5. Open a terminal, change to the election-dapp/frontend directory, then generate types for your election module by running the following command:

   npm run pactjs:generate:contract:election

   npm run pactjs:generate:contract:election

   This command uses the pactjs library to generate the TypeScript definitions for the election contract and should clear the errors reported by the code editor. Depending on the code editor, you might need to close the project in the editor and reopen it to reload the code editor window with the change.

6. Review the vote function, remove the @ts-ignore comment, and save your changes to the DevnetVoteRepository.ts file.

7. Open the election-dapp/frontend folder in a terminal shell on your computer.

8. Install the frontend dependencies by running the following command:

   npm install

   npm install

9. Start the frontend application configured to use the development network running locally by running the following command:

   npm run start-devnet

   npm run start-devnet

Cast a vote

1. Verify the development network is currently running on your local computer.

2. Open and unlock the Chainweaver desktop or web application and verify that:

   • You're connected to development network (devnet) from the network list.
   • Your administrative account name with the k: prefix exists on chain 1.
   • Your administrative account name is funded with KDA on chain 1.

   You're going to use Chainweaver to sign the voting transaction.

3. Open http://localhost:5173 in your browser, then click Set Account.

4. Paste your administrative account, then click Save.

5. Click Add Candidate to add candidates, if necessary.

6. Click Vote Now for a candidate row.

7. Sign the transaction, and wait for the transaction to finish.

8. Verify that the number of votes for the candidate you voted for increased by one vote.

   After you vote, the Vote Now button is disabled because the frontend checks if your account has already voted by making a local request to the account-voted function of the election Pact module.

   

Next steps

• Organize test cases into separate REPL files.
• Modify the vote function iteratively using test cases and expected results.
• Use the with-default-read function.
• Add a votes database table to store the vote cast by each account holder.
• Connect the voting functionality from the frontend to the development network as a backend.

git checkout 09-gas-station

git checkout 09-gas-station