System Tests Coverage
Latest update: 2024-10-04
Legend: 
CLI User Stories
Status for Story ID |
Title |
Story Overview |
|---|---|---|
Obtain constitution hash for verification (HOLDER) → |
As an Ada holder, I want to obtain the hash of the off-chain text of a Constitution, so that I can compare it against the hash registered on-chain to verify its authenticity. |
|
Generate hash of the off-chain constitution (HOLDER) → |
As an Ada holder, I want to generate the hash of the off-chain text for a proposed Constitution, so that the hash can be utilized in a governance action. |
|
Generate Committee member cold key pair (CCM) → |
As a potential Constitutional Committee member, I want to generate COLD key pair, so that I can be proposed for the Committee in a Governance action. |
|
Generate committee member hot key pair (CCM) → |
As potential Constitutional Committee member, I want to generate HOT key pair, so that I can authorise the Hot key to sign votes on behalf of the Cold key. |
|
Authorization certificate (CCM) → |
As a Constitutional Committee member, I want to issue a authorization certificate from my cold key to a hot key, so that I can sign my votes using the hot key and keep the cold key in cold storage and can authorise a new hot key in case the original one is compromised. |
|
Generate committee member key hash (CCM) → |
As a potential Constitutional Committee member, I want to generate the key hashes for my cold and hot keys, so that they can be used by third parties to propose me as a new Constitutional Committee member and for identification purposes once I’ve been elected as Constitutional Committee member. |
|
Committee member resignation certificate (CCM) → |
As a Constitutional Committee member, I want to be able to generate a resignation certificate, so that I can submit it to the chain on a transaction to signal to the Ada holders that I’m resigning from my duties as CC member. |
|
Generate DRep keys (HOLDER) → |
As an Ada holder, I want to generate Ed25519 keys, so that I can register as a DRep. |
|
Generate DRep ID (DRep) → |
As a DRep, I want to generate a DRep Id, so that Ada holder can use it to delegate their votes to me and my voting record can be tracked. |
|
DRep Registration Certificate Generation (DRep) → |
As a DRep, I want to generate a DRep registration certificate, so that I can submit it on a transaction and the Ada holders can delegate their votes to me. |
|
DRep Retirement Certificate Generation (DRep) → |
As a DRep, I want to generate a DRep retirement (unregistration) certificate, so that I can submit it on a transaction and can get my DRep deposit back. |
|
DRep Metadata Hash Generation (DRep) → |
As a DRep, I want to generate the hash of my DRep metadata, so that I can supply it when registering as DRep. |
|
Create Update Constitution Governance Action (HOLDER) → |
As an Ada holder, I want to create a governance action that updates the constitution, so that it can be submitted to the chain and be voted by the governance bodies. |
|
Create Update Constitutional Committee Governance Action (HOLDER) → |
As an Ada holder, I want to create a governance action that updates the Constitutional Committee, so that it can be submitted to the chain and be voted by the governance bodies. |
|
Create Treasury Withdrawal Governance Action (HOLDER) → |
As an Ada holder, I want to create a governance action to withdraw funds from the treasury, so that it can be submitted to the chain and be voted by the governance bodies.
Command: |
|
Create info governance action (HOLDER) → |
As an Ada holder, I want to create an info governance action, so that it can be submitted to the chain and be voted by the governance bodies.
Command: |
|
Create update protocol parameters governance action (HOLDER) → |
As an Ada holder, I want to create a governance action to update protocol parameters, so that it can be submitted to the chain and be voted by the governance bodies.
Command: |
|
Create no-confidence governance action (HOLDER) → |
As an Ada holder, I want to create a no-confidence governance action, so that it can be submitted to the chain and be voted by the governance bodies.
Command: |
|
Create Hard-fork initiation governance action (HOLDER) → |
As an Ada holder, I want to create a governance action to initiate a hardfork, so that it can be submitted to the chain and be voted by the governance bodies.
Command: |
|
View governance action file (HOLDER) → |
As an Ada holder, I want to inspect the contents of a governance action file, so that I can verify it is correct before submitting it in a transaction.
Command: |
|
Create a governance action vote (DRep/SPO/CCM) → |
As a DRep, SPO or CC member, I want to create a vote for a governance action, so that I can include it in a transaction and submit it to the chain.
Command: |
|
View vote file (DRep/SPO/CCM) → |
As a DRep, SPO or CC member, I want to inspect the contents of a vote file, so that I can verify it is correct before submitting it in a transaction.
Command: |
|
Build a transaction with to submit proposal (HOLDER) → |
As an Ada holder, I want to build a transaction that includes a proposal (containing a governance action), so that I can later sign and submit to the chain.
Command: |
|
Build transaction for proposal vote (DRep, SPO, CCM) → |
As a DRep, SPO or CC member, I want to build a transaction that includes my vote on a particular governance action, so that I can later sign and submit to the chain.
Command: |
|
Build RAW transaction for proposal vote (HOLDER) → |
As an Ada holder, I want to build a transaction that includes a proposal (containing a governance action), so that I can later sign and submit to the chain.
Command: |
|
Build RAW transaction for proposal vote (DRep/SPO/CCM) → |
As a DRep, SPO or CC member, I want to build a transaction that includes my vote on a particular governance action, so that I can later sign and submit to the chain.
Command: |
|
Create stake registration certificate (HOLDER) → |
As an Ada holder, I want to create a conway cddl-compliant stake registration certificate. |
|
Create stake deregistration certificate (HOLDER) → |
As an Ada holder, I want to create a conway cddl-compliant stake deregistration certificate to get my deposit back. |
|
Delegate vote to DRep (HOLDER) → |
As an Ada holder, I want to delegate my votes to a DRep (registered or default), so that my stake is counted when the DRep votes. |
|
Delegate stake to SPO and votes to DRep with a single certificate (HOLDER) → |
As an Ada holder, I want to delegate my stake to a stake pool AND my votes to a DRep (registered or default) with a single certificate. |
|
Query governance state (ANY) → |
As any persona, I want to query the nodes for the currentGovernance state, so that I can inform my decisions. |
|
Query committee state (CCM) → |
As a CC member, I want to query the Constitutional Committee state, so that I can find my expiration term and whether my hot key authorization certificate has been recorded on chain. |
|
Query DRep state (HOLDER) → |
As an Ada holder, I want to query the DRep state, so that I can find detailed information about registered DReps. |
|
Query DRep stake distribution (HOLDER) → |
As an Ada holder and DRep, I want to query the DRep stake distribution, so that I can find the weight (of the votes) of each DRep. |
|
Expand query stake-address-info to show deposits and vote delegation (HOLDER) → |
As an Ada holder, I want to query my stake address information, so that I can learn to which pool and DRep I’m delegating to and the value in lovelace of my deposits for delegating and for submitting governance actions. |
|
Query constitution. → |
As any persona, I want to query the on-chain constitution, so that I can know the url where it is stored and the document hash, so that I can verify authenticity. |
CIP1694 User Stories
Status for Story ID |
Title |
Story Overview |
|---|---|---|
Constitution → |
As a Stakeholder, I want the ledger to maintain a record of the hash value of the current constitution together with a URL hosting the off-chain document, so that I can verify the authenticity of the off-chain document. |
|
Hash value of the off-chain Constitution is recorded on-chain → |
As a Stakeholder, I want the ledger to maintain a record of the hash value of the current constitution together with a URL hosting the off-chain document, so that I can verify the authenticity of the off-chain document. |
|
Node records Committee member key hashes, terms and status → |
As a Stakeholder, I want the key hash of active and expired Committee Members and their terms to be registered on-chain, so that the system can count their votes. |
|
Authorization Certificate → |
As a Committee Member, I want to generate and submit a Cold to Hot Credential Authorization certificate, so that I can sign votes using the hot credential and keep the cold credential in safe storage. |
|
Record cold credentials and authorization certificates on chain → |
As a committee member, I want the ledger to accurately maintain the record of key-hashes, terms, and cold to hot credentials authorization maps for active and expired members, so that only votes from active Committee members count. |
|
Replacing the constitutional committee via a governance action → |
As a Governance Actor, I want to submit a governance action to replace all or part of the current constitutional committee, so that committee members who have lost the confidence of stakeholders can be removed from their role. |
|
Size of the constitutional committee → |
As a Stakeholder, I want the minimal size of the Constitutional Committee to be a protocol parameter, so that it can be adjusted via a governance action. |
|
Committee voting threshold (quorum) can be modified → |
As a Stakeholder, I want the committee quorum (the fraction of committee required to ratify a gov action) to be not fixed, so that it can be modified via a governance action. |
|
Electing an empty committee → |
As a Stakeholder, I want to have the option of electing an empty committee, so that governance actions don’t need the votes of a Constitutional Committee to be ratified. |
|
Constitutional committee members have a limited term → |
As a Stakeholder and as a Committee Member, I want each Committee Member to have an individual term, so that the system can have a rotation scheme. |
|
Tracking committee member expirations → |
As a Stakeholder, I want the system to keep track of the expiration epoch of each committee member, so that the information is publicly available in the ledger and the community can plan ahead and agree on new CC member. |
|
Automatically expire committee members that have completed their terms → |
As a Stakeholder and as a Committee Member, I want the system to automatically expire committee members that have reached their term, so that only votes from active committee members count towards ratification. |
|
Resign as committee member → |
As a committee member, I want to be able to resign my responsibilities, so that I can stop my responsibilities with the Cardano Community while minimizing the effects on the system. |
|
State of no-confidence → |
As a Stakeholder, I want to submit a governance action to depose the current Constitutional Committee and put the system in a no-confidence state, so that the community must elect a new Constitutional Committee. |
|
Constitutional Committee below committeeMinSize → |
As a Stakeholder, I want, when the number of non-expired committee members falls below the minimal size of the committee, only update-committee and no-confidence governance actions can be ratified. |
|
Proposal policy → |
As a Stakeholder, I want the option for the constitution to be accompanied by a script, so that governance actions proposing parameter changes or treasury withdrawals that violate accepted limits are automatically restricted. |
|
Delegate votes to a registered Delegate Representatives → |
As a Stakeholder, I want to delegate voting rights to a registered Delegate Representative (DRep), so that I can participate in the governance of the system backing up votes with my stake. |
|
Delegate to always abstain → |
As a Stakeholder, I want to delegate my stake to the predefined option ‘Abstain’, so that my stake is marked as not participating in governance. |
|
Delegate to no-confidence → |
As a Stakeholder, I want to delegate my stake to the predefined DRep ‘No Confidence’, so that my stake is counted as a ‘Yes’ vote on every ‘No Confidence’ action and a ‘No’ vote on every other action. |
|
Inactive DReps → |
As an Ada holder, I want DReps to be considered inactive if they don’t vote for |
|
DRep credentials → |
As a DRep, I want to be identified by a credential that can be a verification key (Ed25519) or a Native or Plutus Script, so that I can register and vote on governance actions with a signing key or with the evaluation of a script logic. |
|
DRep registration certificate → |
As a DRep, I want to generate and submit a registration certificate, so that the system recognizes my credentials and counts my votes on governance actions proportionally to the voting stake delegated to me. |
|
Vote delegation certificate → |
As a Stakeholder, I want to generate a vote delegation certificate, enabling me to delegate my voting rights to either a default or a registered DRep. |
|
DRep retirement certificate → |
As a DRep, I want to generate and submit a retirement certificate, so that the system and stakeholders know that I’m no longer voting on governance actions and that stakeholders should re-delegate. |
|
DRep retirement certificate is applied immediately after being accepted on-chain → |
As a DRep, I want my retirement certificate to be applied immediately upon acceptance on-chain, with the DRep deposit returned in the same transaction, ensuring no waiting time. |
|
per-DRep stake distribution → |
As an Ada Holder, I want the system to calculate the stake distribution per DRep, so that each DRep’s vote is weighted according to the actual stake delegated to them. This per-DRep stake distribution should use the stake snapshot from the last epoch boundary. |
|
Bootstrapping phase → |
||
Block rewards withdrawals for stake credentials that are not delegating to a DRep → |
As a Stakeholder, I want that when bootstrapping phase ends, the system blocks rewards withdrawals for stake credentials that are not delegating to a DRep. |
|
Types of governance actions → |
As a Stakeholder, I want the governance system to allow 7 different types of governance actions:
|
|
Governance action initiation → |
As a Stakeholder, I want any stakeholder to be able to submit a governance action without restrictions, beyond those necessary for a transaction of this type to be considered valid. |
|
Governance action initiation → |
As a Stakeholder, I want Governance Actors to be required to provide a deposit in lovelace, so that I can prevent the network from being spammed with meaningless governance actions. This deposit should be returned once the action is either ratified or expired. |
|
Contents of governance actions → |
As a Governance Actor, I want every governance action to contain the following elements:
|
|
New committee/threshold GA additional data → |
As a Governance actor creating a New Committee governance action, I want to specify the following additional data:
|
|
Update the constitution GA additional data → |
As a Governance actor creating a Update to the constitution GA, I want to include an anchor to the Constitution and an optional script hash of the proposal policy. |
|
Hardfork initiation GA additional data → |
As a Governance actor creating a hardfork initiation governance action, I want to include the new (greater) major protocol version. |
|
Protocol parameter changes GA additional data → |
As a Governance actor creating a protocol parameter change GA, I want to include the parameter to change and their new values. |
|
Treasury withdrawal GA additional data → |
As a governance actor creating a treasury withdrawal GA, I want to include a map from stake credentials to a positive number of Lovelace. |
|
Governance action maximum lifetime → |
As a Stakeholder, I want governance actions submitted in a transaction and admitted to the chain to remain active for up to govActionLifetime epochs, so that these actions are checked for ratification at every epoch boundary within their govActionLifetime. If an action gathers enough ‘yes’ votes to meet the thresholds of the governing bodies, it is ratified; otherwise, if it fails to gather sufficient ‘yes’ votes during the active period, the proposal expires and is removed. |
|
Enactment of ratified actions → |
As a Stakeholder, I want ratified actions to be automatically enacted at the next epoch transition following their ratification. |
|
Governance action deposit returns → |
As a Governance Actor, I want governance action deposits to be returned immediately after ratification or expiration. |
|
Deposits count towards voting power (stake) → |
Governance action deposits are added to the deposit pot and count towards the stake of the reward address to which they will be returned, to ensure that the proposer can back their own action with their voting power. |
|
Proposal policy → |
As a Stakeholder, I want governance actions that attempt to change protocol parameters or involve treasury withdrawals to include the supplementary script from the constitution in the witness set, either directly or via reference inputs, whenever such a script exists. |
|
Multiple protocol parameter updates → |
As a Governance Actor, I want a governance action to allow multiple protocol parameter changes at once. |
|
Delay of ratification → |
As a Stakeholder, I want the ratification of all other governance actions to be delayed until the first epoch following the enactment of a successful motion of no-confidence, the election of a new Constitutional Committee, a constitutional change, or a hard-fork. |
|
Motion of no confidence, requirements for ratification → |
As a Stakeholder, I want that the ratification of a Motion of no confidence governance action requires:
|
|
New committee/threshold (normal state), requirements for ratification → |
As a Stakeholder, I want that the ratification of a New committee/threshold (normal state) governance action requires:
|
|
New committee/threshold (state of no-confidence), requirements for ratification → |
As a Stakeholder, I want that the ratification of a New committee/threshold (state of no-confidence) governance action requires:
|
|
Update to the Constitution or proposal policy, requirements for ratification → |
As a Stakeholder, I want that the ratification of a Update to the Constitution or proposal policy governance action requires:
|
|
Hard-fork initiation, requirements for ratification → |
As a Stakeholder, I want that the ratification of a Hard-fork initiation governance action requires:
|
|
Protocol parameter changes, network group → |
As a Stakeholder, I want that the ratification of a network group protocol parameter change requires:
|
|
Protocol parameter changes, economic group → |
As a Stakeholder, I want that the ratification of a economic group protocol parameter change requires:
|
|
Protocol parameter changes, technical group → |
As a Stakeholder, I want that the ratification of a technical group protocol parameter change requires:
|
|
Protocol parameter changes, governance group → |
As a Stakeholder, I want that the ratification of a governance group protocol parameter change requires:
|
|
Treasury withdrawal, requirements for ratification → |
As a Stakeholder, I want that the ratification of a Treasury withdrawal governance action requires:
|
|
The network group protocol parameters → |
As a Stakeholder, I want the network group consist of:
|
|
The economic group protocol parameters → |
As a Stakeholder, I want that the economic group consist of:
|
|
The technical group protocol parameters → |
As a Stakeholder, I want that the technical group consist of:
|
|
The governance group protocol parameters → |
As a Stakeholder, I want that the governance group consist of:
|
|
Thresholds for Info is set to 100% → |
As a Stakeholder, I want the two thresholds for the Info action be set to 100% since setting it any lower would result in not being able to poll above the threshold. |
|
Preventing accidental clash of actions of the same type → |
As a Stakeholder, I want all governance actions, except for Treasury withdrawals and Infos, to include the governance action ID of the most recently enacted action of the same type, so that accidental clashes between actions can be prevented. |
|
Governance action enactment prioritization → |
As a Stakeholder, I want actions that have been ratified in the current epoch to be prioritized for enactment in the following order:
|
|
Governance action order of enactment → |
As a Stakeholder, I want governance actions to be enacted in the order of their acceptance to the chain. |
|
Governance actions automatic enactment → |
As a Stakeholder, I want ratified actions to be automatically enacted at the next epoch boundary. |
|
No duplicate committee members → |
As a Stakeholder, I want each pair of credentials in a committee to be unique, ensuring no duplicate committee members. |
|
Governance action ID → |
As a Stakeholder, I want the transaction ID and index of the transaction that submits the governance action to the chain to serve as the governance action ID, so that this ID shall would be used for casting votes. |
|
Vote transactions contents → |
As a Stakeholder, I want each vote transaction to consist of the following elements:
|
|
SPO and DREP votes are proportional to the stake delegated to them → |
For SPOs and DReps, the number of votes cast (‘Yes’, ‘No’, or ‘Abstain’) shall be proportional to the amount of Lovelace delegated to them at the time the action is checked for ratification. |
|
CC votes → |
As a Stakeholder, I want each current committee member to have one vote. |
|
Active voting stake → |
As a Stakeholder, I want the active voting stake to be the total registered stake minus the abstain votes stake (both credential DReps and AlwaysAbstain). |
|
Unregistered stake behaves like Abstain vote → |
As a Stakeholder, I want unregistered stake to be treated as an abstain vote, so that it should not count towards the active voting stake. |
|
Registered stake that did not vote behaves like a ‘No’ vote → |
As a Stakeholder, I want any registered stake that did not submit a vote, whether through its DRep or SPO, to be counted as a ‘No’ vote. |
|
New Plutus script purpose for scripts → |
As a Stakeholder, I want a new voting purpose for Plutus scripts. |
|
Any new vote overrides any older vote for the same credential and role → |
As a Stakeholder, I want new votes on a governance action to override any previous votes for the same credential and role, so that individuals could change their minds. |
|
Voting ends when an action is ratified and transactions containing further votes are invalid → |
As a Stakeholder, I want the voting period to terminate immediately after an action is ratified or expires. |
|
Governance state tracking governance action progress → |
As a Stakeholder, I want the governance state section of the ledger to track the progress of governance actions to include: capturing votes, tracking the expiration epoch, and other relevant information until the actions are either ratified or expired. |
|
Remove MIR certificates → |
As a Stakeholder, I want MIR certificates to be removed, so that the only way to withdraw funds from the treasury is through a ratified Treasury Withdrawal governance action. |
|
Remove genesis certificates → |
As a Stakeholder, I want genesis certificates to be removed. In Conway era these are no longer useful or required. |
|
Changes to the existing ledger rules → |
As a Stakeholder, I want the ledger to adjust its rules to accommodate for the governance features, i.e. Delegations, Certificates, Proposals, Votes, Ratification, Enactment. |
|
Changes to the local state-query protocol → |
As a Stakeholder, I want the ledger to adjust the local state query protocol to accommodate for new queries that provide insights about governance, at least:
|
|
Ratification of Security related parameters → |
The security relevant protocol parameters require the approval of the three governing bodies.
|
|
Auditor review of current network parameters → |
As an Auditor, I want to audit the current state of the network parameters, so that I can ensure they align with the governance decisions. |
|
Auditor review of current technical parameters → |
As an Auditor, I want to audit the current technical parameters, including consenus and cost models, so that I can ensure their compliance with the network parameters specified. |
|
Auditor review of current economic parameters → |
As an Auditor, I want to audit the current economic parameters, including parameters affecting transaction fees, taxes, and staking rewards, so that I can assess their impact on the network’s economy. |
|
Auditor review of current governance parameters and voting thresholds → |
As an Auditor, I want to audit the current governance parameters and voting thresholds for governance actions to fail or ratify, so that I can verify their appropriateness and adherence to governance rules, adherence to the constitution, and enforcement of voting thresholds. |
|
Auditor review of current state of the treasury → |
As an Auditor, I want to audit the current state of the treasury, including the total amount of Ada, so that I can assess the current balance and the system’s financial health. |
|
Auditor needs access to historical proposals affecting network parameters → |
As an Auditor, I want to access and review the history of proposals related to network parameters, including their outcomes, so that I can track governance effectiveness over time. |
|
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, so that I can understand technical evolution and parameter change impact. |
|
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, so that I can evaluate economic policy changes. |
|
Auditor needs access to the historical record of all governance proposals and voting thresholds → |
As an Auditor, I want to access history changes to governance parameters, the proposals, and the voting thresholds, so that I can audit the changes made over time and 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. |
|
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, so that I can ensure transparency and accountability. |
|
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. |
|
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. |
|
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. |
|
No delegation without stake registration → |
As a stakeholder, I should not be able to delegate my votes without registering my stake address first. |
|
No retirement before register → |
As a DRep, I should not be able to retire my DRep before registering it. |
|
No multiple DRep registration → |
As As a DRep, I should not be able to register my DRep multiple times using the same DRep credentials. |
Governance guardrails User Stories
Status for Story ID |
Title |
Story Overview |
|---|---|---|
Prevent an unconstitutional txFeePerByte value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for txFeePerByte. |
|
Prevent an unconstitutional txFeeFixed value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for txFeeFixed. |
|
Prevent an unconstitutional monetaryExpansion value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for monetaryExpansion. |
|
Prevent an unconstitutional treasuryCut value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for treasuryCut. |
|
Prevent an unconstitutional minPoolCost value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for minPoolCost. |
|
Prevent an unconstitutional utxoCostPerByte value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for utxoCostPerByte. |
|
Prevent an unconstitutional executionUnitPrices [priceMemory] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for executionUnitPrices[priceMemory]. |
|
Prevent an unconstitutional executionUnitPrices [priceSteps] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for executionUnitPrices[priceSteps]. |
|
Prevent an unconstitutional maxBlockBodySize value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxBlockBodySize. |
|
Prevent an unconstitutional maxTxExecutionUnits [memory] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxTxExecutionUnits[memory]. |
|
Prevent an unconstitutional maxTxExecutionUnits [steps] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxTxExecutionUnits[steps]. |
|
Prevent an unconstitutional maxBlockExecutionUnits [memory] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxBlockExecutionUnits[memory]. |
|
Prevent an unconstitutional maxBlockExecutionUnits [steps] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxBlockExecutionUnits[steps]. |
|
Prevent an unconstitutional maxValueSize value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxValueSize. |
|
Prevent an unconstitutional collateralPercentage value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for collateralPercentage. |
|
Prevent an unconstitutional maxCollateralInputs value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxCollateralInputs. |
|
Prevent an unconstitutional poolVotingThresholds [motionNoConfidence] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolVotingThresholds[motionNoConfidence]. |
|
Prevent an unconstitutional poolVotingThresholds [committeeNormal] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolVotingThresholds[committeeNormal]. |
|
Prevent an unconstitutional poolVotingThresholds [committeeNoConfidence] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolVotingThresholds[committeeNoConfidence]. |
|
Prevent an unconstitutional poolVotingThresholds [hardForkInitiation] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolVotingThresholds[hardForkInitiation]. |
|
Prevent an unconstitutional poolVotingThresholds [ppSecurityGroup] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolVotingThresholds[ppSecurityGroup]. |
|
Prevent an unconstitutional dRepVotingThresholds [motionNoConfidence] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[motionNoConfidence]. |
|
Prevent an unconstitutional dRepVotingThresholds [committeeNormal] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[committeeNormal]. |
|
Prevent an unconstitutional dRepVotingThresholds [committeeNoConfidence] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[committeeNoConfidence]. |
|
Prevent an unconstitutional dRepVotingThresholds [updateToConstitution] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[updateToConstitution]. |
|
Prevent an unconstitutional dRepVotingThresholds [hardForkInitiation] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[hardForkInitiation]. |
|
Prevent an unconstitutional dRepVotingThresholds [ppNetworkGroup] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[ppNetworkGroup]. |
|
Prevent an unconstitutional dRepVotingThresholds [ppEconomicGroup] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[ppEconomicGroup]. |
|
Prevent an unconstitutional dRepVotingThresholds [ppTechnicalGroup] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[ppTechnicalGroup]. |
|
Prevent an unconstitutional dRepVotingThresholds [ppGovGroup] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[ppGovGroup]. |
|
Prevent an unconstitutional dRepVotingThresholds [treasuryWithdrawal] value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepVotingThresholds[treasuryWithdrawal]. |
|
Prevent an unconstitutional committeeMinSize value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for committeeMinSize. |
|
Prevent an unconstitutional committeeMaxTermLimit value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for committeeMaxTermLimit. |
|
Prevent an unconstitutional govActionLifetime value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for govActionLifetime. |
|
Prevent an unconstitutional maxTxSize value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxTxSize. |
|
Prevent an unconstitutional govDeposit value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for govDeposit. |
|
Prevent an unconstitutional dRepDeposit value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepDeposit. |
|
Prevent an unconstitutional dRepActivity value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for dRepActivity. |
|
Prevent an unconstitutional minFeeRefScriptCoinsPerByte value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for minFeeRefScriptCoinsPerByte. |
|
Prevent an unconstitutional maxBlockHeaderSize value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for maxBlockHeaderSize. |
|
Prevent an unconstitutional stakeAddressDeposit value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for stakeAddressDeposit. |
|
Prevent an unconstitutional stakePoolDeposit value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for stakePoolDeposit. |
|
Prevent an unconstitutional poolRetireMaxEpoch value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolRetireMaxEpoch. |
|
Prevent an unconstitutional stakePoolTargetNum value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for stakePoolTargetNum. |
|
Prevent an unconstitutional poolPledgeInfluence value → |
As an ADA holder, when submitting an update protocol parameters proposal, the governance guardrail should prevent an unconstitutional value for poolPledgeInfluence. |
DB Sync - Conway related tables
Status for table |
Description |
|---|---|
A table for every unique drep key hash. The existence of an entry doesn’t mean the DRep is registered. → |
|
A table for all committee credentials hot or cold. → |
|
A table containing delegations from a stake address to a stake pool. → |
|
A table for every committee hot key registration. → |
|
A table for every committee key de-registration. → |
|
A table for DRep registrations, deregistrations or updates. Registration have positive deposit values, deregistrations have negative and updates have null. Based on this distinction, for a specific DRep, getting the latest entry gives its registration state. → |
|
A table for every Anchor that appears on Governance Actions. These are pointers to offchain metadata. The tuple of url and hash is unique. → |
|
A table for proposed GovActionProposal, aka ProposalProcedure, GovAction or GovProposal. This table may be referenced by TreasuryWithdrawal or NewCommittee. → |
|
A table for all treasury withdrawals proposed on a GovActionProposal. → |
|
A table for new committee proposed on a GovActionProposal. → |
|
A table for members of the committee. A committee can have multiple members. → |
|
A table for constitution attached to a GovActionProposal. → |
|
A table for voting procedures, aka GovVote. A Vote can be Yes No or Abstain. → |
|
The table for the distribution of voting power per DRep per. Currently this has a single entry per DRep and doesn’t show every delegator. This may change. → |
|
The table with the offchain metadata related to Vote Anchors. It accepts metadata in a more lenient way than what’s described in CIP-100. → |
|
The table with offchain metadata for Governance Actions. Implements CIP-108. → |
|
The table with offchain metadata for Drep Registrations. Implements CIP-119. → |
|
The table with offchain metadata authors, as described in CIP-100. → |
|
The table with offchain metadata references, as described in CIP-100. → |
|
The table with offchain metadata external updates, as described in CIP-100. → |
|
Errors while fetching or validating offchain Voting Anchor metadata. → |
|
A table containing block chain parameter change proposals. → |
|
The accepted protocol parameters for an epoch. → |
