Working with the current schema

See also: Metadata schema

• Here is an example attestation.
• We can query based on the uid in OSO:
• The fields were care about are about from the raw attestation data are:
• From the metadata url, we can get the attestation metadata, eg:
• From the metadata, we need the values at:
• Thus, the normalized data we want is:

Backup: Future schema iterations

• A more flexible variant of the metadata schema might…

Data for the voting client

The voting client will surface impact attestation data from a JSON that contains the following:

{
    "uid": "0x0c845fd444022ef274699b918996c1e3a3ad7887fd92083646bce3df9d7a4922",
    "attester": "0x13a5995756acf96e62b80009d37538f140370e37",
    "rf6_applicationUID": "0x59ccc24d38de83c3db70f5326d3d12ddcbca3fc9eb1eeb3df57322f730662f2f",
    "pmf_score": 2,
    "nps_score": 1,
    "is_citizen": true,
    "is_top_delegate": false,
    "governance_membership": [
      "Anticapture Commission",
      "Developer Advisory Board"
    ]
  },

Here is an example of some dummy data that follows this schema.

1. Number of Attestations (only want the count from Citizens and Top Delegates)
2. Number of Attestations by Citizens
3. Number of Attestations by Top delegates