| SC1 |
A user who is new to Catalyst can understand how to vote in 5 minutes maximum. |
| SC2 |
A user should be able to stop voting and restart voting without loosing votes |
| SC3 |
If a user tries to vote on the same proposal twice he will receive a clear error message |
| SC4 |
After a user cast a vote he will receive a clear feedback on the status of his vote |
| SC5 |
Proposals are fully loaded and able to be navigated by user in less than 10 seconds |
| SC6 |
Search/sort/ filter results returned in less than 5 seconds |
| SC7 |
User clicks on one of the top 5 search results in at least 80% of search queries |
| SC8 |
A user can vote in less than 3 clicks from loading proposals page |
| SC9 |
A user can vote on another proposal in less than 2 clicks after voting on one proposal |
| SC10 |
User gets confirmation of votes cast in less than 5 seconds |
| SC11 |
User gets confirmation of votes confirmed in less than 30s |
| SC12 |
More than 80% of proposals are submitted to a vote within 6 months of creation |
| SC13 |
Less than 10% of proposals are reassigned to a new category between initial category select & submission |
| SC14 |
Less than 10% of proposals are withdrawn from an event once submitted |
| SC15 |
More than 80% of proposals are ready for submission in less than 10 editing sessions |
| SC16 |
100% of votes confirmed are represented in final tally |
| SC17 |
Less than 5% of votes cast are rejected |
| SC18 |
100% of rejected transactions have known reason |
| SC19 |
100% transactions sent to chain are traceable |
| SC20 |
All voters can be verified against mainnet snapshot |
| SC21 |
All voting power can be verified against mainnet snapshot |
| SC22 |
All votes cast are represented in tally |
| SC23 |
Tally is correctly calculated given all votes |
| SC24 |
User gets new access permissions within 60s of role registration tx confirmation |
| SC25 |
Only registered proposers may create, update, or delete a proposal |
| SC26 |
As a voter, I can only delegate voting power to dreps that have a valid drep registration |
| SC27 |
Only a registered drep may vote with delegated voting power |
| SC28 |
As a user, I need to sign my votes with a voter key |
| SC29 |
As a user, I need to sign proposal updates with a proposer key |
| SC30 |
As a user, I need to sign my drep votes with a drep key |
| SC31 |
As a user, I need to sign team-owned proposal updates with a team key |
| SC32 |
Able to handle arbitrary configurations of fund parameters |
| SC33 |
Able to handle arbitrary configurations of proposal template |
| SC34 |
Able to handle arbitrary configurations of category template |
| SC35 |
Able to integrate new modules in the future |
| SC36 |
Able to integrate open source community contributions |
| SC37 |
A single event can be administered by a single non technical user |
| SC38 |
Overall platform can be maintained by 1 SRE, 2 SWE, 1 QA |
| SC39 |
Important metrics viewable by non technical users |
| SC40 |
New versions can be deployed by SRE in less than 1 hour |
| SC41 |
On chain immutable record of registrations, proposals, votes, and tally for every event |
| SC42 |
Due Diligence maintained by 3rd party for all relevant user types |
| SC43 |
Up to 1M concurrent users - wallet connect, login, registration, proposal create, comment, vote |
| SC44 |
Up to 100 votes per second |
| SC45 |
Up to 10 people editing the same proposal |
| SC45 |
Up to 50 concurrent brands/customers running parallel events on platform |
| SC46 |
Up to 500 concurrent events/voting rounds |
| SC47 |
Up to 100k proposals |
| SC48 |
Up to 500k comments |
| SC49 |
Up to 250k registered accounts |
| SC50 |
The search click-through rate should be more then 50% |
| SC51 |
As a user, if I mark my proposal private, only I (and my team) can see it |
| SC52 |
As a user, if I mark my proposal as public, anyone can see it |
| SC53 |
As a user, only me and my team can make edits to my proposal |
| SC54 |
Notifications properly delivered to all target accounts |
| SC55 |
Updates to event parameters reflected in less than 1 hour across all users |
| SC56 |
Users always shown accurate dates for an event |
| SC57 |
10% of circulating supply that registers to vote |
| SC58 |
80% of registered stake that submits a vote |
| SC59 |
50% of voting stake that casts at least 25 votes |
| SC60 |
Users should not reach to customer service for help on how to use the system |
| SC61 |
Unit tests should take less then 30 minutes to run |
| SC62 |
Test report should be available and up to date |
| SC63 |
Localizable to several languages |
| SC64 |
Compliance with WCA accessibility guidelines |
| SC65 |
If the system gets more then 100 votes per second votes are not lost |
| SC66 |
User private key are secure |
| SC67 |
New team member can be onboarded without help from the team |
| SC68 |
Tests functions have a comment explaining the steps of the test |