We have added:
04.2020 Add keybase auth via one-time codes and keybase-bot (similar how https://stellarcommunity.fund works) ✓
Additionally, you can specify the team membership requirements, so only members of a particular team can take part in voting. Therefore we can delegate the user authorization process to team owners. It is achieved by using keybase-bot. When the voting is created, stellotbot requests access to a specified keybase team. If the team is open, it automatically joins the team, If not, it waits until the team owners approve the stellotbot request. When the stellotbot can access the team membership list. When a user want to cast a vote in such voting, he enters his Keybase username, and send it to Stellotbot, which ensures that the user is a member of the required team. Stellotbot then sends a signed JWT token to username account in private message. User proof his identity by entering the received JWT token. TDS ensures that the username hasn't already issued the voting token. Now we are ready to issue voting token with blind-signature technique.
Give it a try, this voting is restricted to
stellar.public team members only. Right now the membership is checked on-request, but we are thinking about freezing the list at the time of voting creation, to prevent sockpuppeting accounts.
Monetization is something we will focus on after we create a working prototype. We believe that the demand for secure and private e-voting is something we don't need to worry about (especially nowadays), so the success of this project relies mainly on the properties we are able to achieve. Our undoubted advantage is the fact that user wallet/keypair is completely optional, and we designed the solution on the open Stellar blockchain, which is something we didn't find before. Our first targets are Universities we are associated with, so we already have a solid testing environment.