MCD Voting Tracker Documentation

An explanation of how the MCD Voting Tracker works and what data is available

INTRODUCTION

Access to this version of the MCD Voting Tracker at beta.mcdgov.info is provided under a Beta Program which is described in the Welcome section of the documentation. Access to the Beta Program is under the Terms of Service described in the Legal section of the documentation.

Please read through all sections of the documentation before using the API. In particular we draw your attention to the following:

  • The Beta Program is of limited duration - it may be suspended or ended at any time, but we will endeavour to give participants of the Beta Program as much notice as is reasonably possible before the Beta Program is wound down through messages on the dashboard;

  • As with all Betas, the dashboard, API and underlying dataset and technology are still in development, therefore you can expect to experience bugs, errors, and partial or complete loss of service at any time during the Beta Program. As such you should treat the data as being in development and should not use them for any purpose other than testing and providing feedback during the Beta Program;

  • As described in the documentation below, the data is uploaded every 15 minutes and is not live to the latest block. Since the data is processed before it is made available, the data is typically multiple blocks behind the actual latest block on the public Ethereum blockchain;

  • The dataset includes only information that has been drawn from public sources - no additional data is added - it is just processed for easier access. This means that data particularly in relation to recent blocks may be subject to change e.g. due to chain reorganizations.

PROVIDING FEEDBACK

We welcome feedback from users on this Beta product. We will occasionally request feedback from participants of the Beta Program, for example through Typeform surveys, and you can contact us directly at [email protected].

USING THE DASHBOARD

Data Sourcing and Updating:

Data is objective data sourced from the following - no additional information is added to this public data:

  1. Full history of DSChief contracts (currently v. 1.0, 1.1 and 1.2),

  2. All current Polling contracts (basic and batch polling),

  3. Governance Portal API (titles of executives/polls/options).

Data is automatically reloaded every 15 minutes

Using the Dashboard:

The MCD Voting Tracker at beta.mcdgov.info is a simple dashboard or Graphical User Interface (“GUI”) where you can search manually by Governance Polls, Executive Vote or Voters that you are interested in and see all results related to your search, or you can simply view the summary results presented in the GUI and click through the various links to go deeper into the dataset.

In the following sections of the documentation, we summarize the various views in the GUI and outline the main results available in each view.

Main page:

The following information is shown in this page:

  1. Staked MKR - total amount of MKR in all monitored DSChief contracts.

  2. Executive Votes table (with the current hat marked in green):

    1. Executive address,

    2. Issue date,

    3. Executive title,

    4. Current amount of supporting MKR,

    5. Total number of voters.

  3. Governance Polls table:

    1. Poll number,

    2. Issue date,

    3. Poll title,

    4. Winning option name.

  4. Voters table - current data about all addresses that ever had non-zero stake of MKR:

    1. Voter address,

    2. Currently staked MKR,

    3. List of executives that are currently supported by staked MKR (can be many),

    4. Date when first MKR were staked,

    5. Date of the last voting operation.

Address page:

The following information is shown in this page:

  1. Full voter’s address.

  2. Amount of currently staked MKR.

  3. Link to the Etherscan address page.

  4. Date of the last vote.

  5. Date when first MKR were staked.

  6. Chart of MKR stake in time.

  7. Operations history (decisive operations are marked green):

    1. UTC time of an operation.

    2. Name of an operation (also a link to EthTx.info decoded transaction data):

      1. STAKE - transfer of MKR to DSChief,

      2. WITHDRAW - transfer of MKR from DSChief,

      3. VOTE - placing all staked MKR on the Executive,

      4. UP-VOTE - increasing the approval due to STAKE operation,

      5. DOWN-VOTE - reducing the approval due to WITHDRAW operation,

      6. MOVE VOTE - moving all the staked MKR from the Executive,

      7. CHOOSE - selecting an option in a Governance Poll,

      8. DROP - dropping an existing HAT,

      9. LIFT - lifting a new HAT.

    3. Amount of transferred MKR (in case of STAKE and WITHDRAW).

    4. Total stake after the operation.

    5. Title of Executive (in case of VOTE, UP-VOTE, DOWN-VOTE, MOVE VOTE, DROP or LIFT) or title of Governance Poll (in case of CHOOSE).

    6. Decisive YES / NO - indication whether the operation was raising the total approval vote to the level that enables lifting a new Hat.

Executive Vote page:

The following information is shown in this page:

  1. Title of the Executive Vote.

  2. Current amount of supporting MKR.

  3. Issue date.

  4. Number of voters.

  5. Date of the last vote.

  6. Chart of MKR approval in time.

  7. List of the top supporters:

    1. Address,

    2. Top stake (high water mark).

  8. Voting history (operations in periods when this Executive was a Hat are marked green):

    1. UTC time of an operation,

    2. Voting address,

    3. Name of an operation:

      1. VOTE - placing all staked MKR on the Executive,

      2. UP-VOTE - increasing the approval due to STAKE operation,

      3. DOWN-VOTE - reducing the approval due to WITHDRAW operation,

      4. MOVE VOTE - moving all the staked MKR from the Executive,

      5. DROP - dropping an existing HAT,

      6. LIFT - lifting a new HAT.

  9. Decisive YES / NO - indication whether the operation was increasing the total approval vote to the level that enabled lifting of new Hat (it does not necessarily mean lifting the Hat, because e.g. approval might drop before Governance Keeper takes any action).

  10. Hat YES / NO - indication whether the Executive was a Hat in the moment of the operation.

Governance Poll page:

The following information is shown in this page:

  1. Title of the Governance Poll.

  2. Total amount of supporting MKR (high water mark).

  3. Issue date.

  4. Number of voters.

  5. Date of the last vote.

  6. List of the poll’s options (winning option is marked green):

    1. Option id,

    2. Option title,

    3. Total amount of supporting MKR (high water mark),

    4. Total number of unique voters (high water mark).

  7. Voting history:

    1. UTC time of an operation,

    2. Voting address,

    3. Name of an operation - always ‘CHOOSE’,

    4. Name of selected option (or ‘Not valid’ if selected option was not legit),

    5. Approval (voter’s MKR stake in the moment of the operation).