Relayer scope:

• Validate user eligibility to vote
• Accept the encrypted package
• Relay encrypted user votes to voting contract
• Double vote works

As a Product Owner I want to decrypt votes in order to process voting results
AC1: Decryption keys are available after the voting ends
AC2: Relayer decrypts voting data using keys from AC1 and publishes it to the NEAR mainnet
AC3: Every user can check data published in AC2

@akorchyn @VlodkoMr

Nomination criteria to be defined.

As a Product manager I want to have staking data for the voting project

AC1: I have list of users (accounts) who ever staked

AC2: I have stake amount for users who ever staked at the moment of the snapshot

As a user I want to encrypt data using secret network to preserve my privacy
AC1: User can create a shared secret to encrypt the vote
AC2: Public key for decryption is available after voting period ends

As a Product Manager I want to understand if we have all needed data in the Bigquery public dataset

https://near.org/blog/near-protocol-bigquery-public-dataset.

AC: We outline data that we have and that we do not hace from data needed for voting

As a User I want my vote to be processed in order to get it accounted
AC1: Encrypted votes are stored in the voting contract

As a FE developer I want to have support for filtering snapshot data in order to provide user friendly views
AC1: Following fields are available for filtering\sorting with pagination : (AccountId,ActivityVP,StakingVP,OverallVP,AccountAge)

As a Product Manager I want to have activity data for users that ever staked on NEAR blockchain
AC: We have list of users who ever staked on NEAR with number of months they had an active transaction

As a Product Manager I want to have snapshot in form of json file on IPFS

AC1: Snapshot is available for the block specified in the Election framework document

The scope of the voting contract:

• Store encrypted votes
• Store results
• View methods to get paginated votes and results.

As a Product Manager I want voting package to be encrypted so information about it is not available before the voting ends
AC1: User can create an encryption key
AC2: User can encrypt the Voting package with the key from AC1
AC3: Voting package from AC2 contains amount of votes for each candidate
AC4: User can resubmit the voting untill the end of the voting period
AC5: User is able to submit encryption key from AC1 to the contract

The given work on voting snapshot will require a lot of processing on the data. That might be costly using bigquery api that's why we have to move it first to our local server.

As a user I want to register in voting in order to vote
AC1: Users are able to register in voting
AC2: Same user cant register twice
AC3: Voting power is assigned to user once he registers
AC4: Data about registered users is available on the relayer