trust-vote-site's Introduction

trust-vote-site

Dash Trust Elections - MNO Voting Site

Uses @dashevo/dashcore-lib to verify signatures in-browser.

Hint: Messages are signed the same in Dash-QT as with dash-cli:

./private-key.wif:

XK5DHnAiSj6HQNsNcDkawd9qdp8UFMdYftdVZFuRreTMJtbJhk8i

my_private_key="$(cat ./private-key.wif)"

my_vote='dte2019-efigaro|lcole|sfigaro|cchere'

dash-cli signmessagewithprivkey \
    "${my_private_key}" \
    "${my_vote}"

H3B3fGVZM2joBDmuTptj7gPI0bTFWWE1YZEPoB/5TtYudBRmiP0zszPmtUPqVQJrQzzL2rVgEOdcUAcZNbEzne0=

Alternatively, you can use dashmsg:

curl https://webinstall.dev/dashmsg | bash
export PATH="$HOME/.local/bin:$PATH"

dashmsg sign ./private-key.wif  "dte2019-efigaro|lcole|sfigaro|cchere"

H3B3fGVZM2joBDmuTptj7gPI0bTFWWE1YZEPoB/5TtYudBRmiP0zszPmtUPqVQJrQzzL2rVgEOdcUAcZNbEzne0=

Project Structure

.
├── README.md
├── example.env
├── package-lock.json
├── package.json
├── public/
│   ├── favicon.ico
│   ├── index.html
│   └── manifest.json
├── build/
│   └── ...
└── src/
    ├── apis/
    │   └── dtevote.js
    ├── candidates.json
    ├── components/
    │   ├── App.js
    │   ├── CandidateList.css
    │   ├── CandidateList.js
    │   ├── CandidateSelector.css
    │   ├── CandidateSelector.js
    │   ├── Closed.js
    │   ├── DashLogo.js
    │   └── VoteMessage.js
    ├── index.js
    └── logo.svg

Pre-Reqs

Get Node.js

# Mac & Linux
curl https://webinstall.dev/node | bash

# Windows
curl.exe -A MS https://webinstall.dev/node | powershell

Setup

Clone the project

git clone https://github.com/dashevo/trust-vote-site
pushd ./trust-vote-site/

Configure with .env

rsync -avhP ./example.env ./.env

.env:

# necessary to get the fatty mcfat-fat react app to build
NODE_OPTIONS='--max-old-space-size=4096'

# season to taste
PUBLIC_URL='https://vote.example.com'

REACT_APP_API_URL='https://vote-api.example.com'

REACT_APP_CANDIDACY_FORM_URL='https://docs.google.com/forms/...'

# the ISO+Offset time when voting will start and end
REACT_APP_VOTING_END_DATE='2022-04-03T00:00:00Z'
REACT_APP_VOTING_END_DATE='2022-04-15T00:00:00Z'

# a unique vote identifier as part of the message hash
REACT_APP_VOTE_PREFIX='dte2022-'

REACT_APP_DASH_NETWORK='testnet'

# additional REACT_APP_* will be made available to the browser

Manually update candidates.json

[
  {
    "alias": "name3",
    "text": "Cyrus Tafti",
    "value": "ctafti",
    "key": "ctafti"
  }
]

Run the build
```
npm ci
npm run build
```

Dev-Only Setup

npm run start

Note: Probably best to avoid running in "dev mode" since it doesn't closely resemble production mode... however, it is a LOT faster.

CRApp

This project was bootstrapped with Create React App.

License

MIT © Dash Core Group, Inc.

trust-vote-site's People

Contributors

Watchers

trust-vote-site's Issues

Trust Protector Software Specification

Update vote.dashtrust.org:

Tests to know software is complete and working

Summary Videos

Make (and link voting site to) video(s) showing how to do the following:
- ~~Apply to be a Trust Protector candidate~~
- Vote for candidates (as a masternode voter)
- Tally votes (as an auditor)

Notes for editing and supplementing the draft summary videos:

Explain that Dash Core wallet's debug console is the same as the dash-cli tool - that it accepts the same commands, just without the dash-cli part. Show them how to get to the console in their wallet.
Add a clip showing MNOs visually how to get their voting address from the masternode tab of the Dash Core wallet, as an alternative to using masternode list json ENABLED in the debug console.
Add a clip showing MNOs how to sign a message using the sign message menu in the Dash Core GUI.
Mention that MNOs can ask their operator to do this for them if their nodes are hosted by someone.
~~Maybe remove the part about signing with a private key (file) in case some MNOs try to do that with their collateral private keys where something could go wrong, or at least give proper warnings.~~