Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of new user stories to 01-cip1694 for new tests to be added on cardano-node-tests #45

Merged
merged 1 commit into from
Jun 18, 2024
Merged

Addition of new user stories to 01-cip1694 for new tests to be added on cardano-node-tests #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/inventory/01-cip1694.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,4 +110,10 @@ forbid push to main
| <a id="CIP81"></a>CIP.081 | Auditor needs access to historical proposals affecting technical parameters |As an Auditor, I want to access and review the history of proposals related to technical parameters, including both ratified and failed proposals, to understand technical evolution and parameter change impact. | GovTool/db-sync |
| <a id="CIP82"></a>CIP.082 | Auditor needs access to historical proposals affecting economic parameters | As an Auditor, I want to access and review the history of proposals related to economic parameters, focusing on their ratification status, to evaluate economic policy changes. | GovTool/db-sync |
| <a id="CIP83"></a>CIP.083 | Auditor needs access to the historical record of all governance proposals and voting thresholds | As an Auditor, I want to have access to the history changes to governance parameters, the proposals, and the voting thresholds. I want to audit the changes made over time, and to verify compliance with governance rules, and evaluate the impact of these changes on governance actions' outcomes, with the primary purpose to verify voting thresholds were enforced. | GovTool/db-sync |
| <a id="CIP84"></a>CIP.084 | Auditor needs access to the history of treasury withdrawals | As an Auditor, I want to audit the history of treasury withdrawals, including amounts, dates, and recipient wallet addresses, to ensure transparency and accountability. | GovTool/db-sync |
| <a id="CIP84"></a>CIP.084 | Auditor needs access to the history of treasury withdrawals | As an Auditor, I want to audit the history of treasury withdrawals, including amounts, dates, and recipient wallet addresses, to ensure transparency and accountability. | GovTool/db-sync |
| <a id="CIP85"></a>CIP.085 | DRep Id is blake2b-224 of drep vkey | As a DRep, I want to verify proper Drep Id is being generated that is it should be outcome of blake2b-224 hash of DRep verification key. | Node/CLI |
| <a id="CIP86"></a>CIP.086 | Change delegation | As a stakeholder, I want to change my voting delegation to a different Drep. After I have first delegate to a DRep say DRep 1 I want to change my delegation to another Drep 2, my vote delegation should be updated to Drep2. | Node |
| <a id="CIP87"></a>CIP.087 | No multiple delegation | As a stakeholder, I should not be able to submit multiple voting delegations to different Dreps. The voting rights should be delegated to a single DRep only, even If I submit multiple voting delegation certificates. | Node |
| <a id="CIP88"></a>CIP.088 | No delegation without stake registration | As a stakeholder, I should not be able to delegate my votes without registering my stake address first. | Node |
| <a id="CIP89"></a>CIP.089 | No retirement before register | As a DRep, I should not be able to retire my DRep before registering it. | Node |
| <a id="CIP90"></a>CIP.090 | No multiple DRep registration | As a DRep, I should not be able to register my DRep multiple times using the same DRep credentials. | Node |