Feedback: Schema

[DistributedDoge]

From a perspective of a person that took part in sybil-seeking hackathon, being provided a schema + db like this would have been pretty nice. On the other hand - if you are looking at a single round, a flat .csv file with votes is probably a great low-effort starting point to jump into doing analysis.

Possible additions to existing schema:

• For each transaction that carries a vote it would be nice to know gas i.e. gas price + gas spent.
• Likewise for each project that did apply to round on-chain I would like to see hash of transaction used to do that (+ gas fee).
• Reporting blockNumbers for vote is nice, would be even nicer if there was also approximate_timestamp for plotting timeseries.

Key friction for me usability wise, is that I want to get clean, processed data from authoritative source without having to re-run the pipelines myself.

Interesting external information about each voter/grant address: POAPs, ENS name history, Snapshot votes

[ccerv1]

Shared these with owocki on TG, but here's some additional schema feedback:

• include payoutAddress for a projectInRound (this is the wallet address that receives grant funds) ... I noticed that grantAddress is included in the vote
• include the githubUrl of the project/user who posted the projectInRound (this may be explicitly linked in the application or in other cases the Github username of the account leading the project)

note: these field may both be in the application metadata already, but even so would be preferable to have easily accessible

• include 'chain' in the 'vote' table

• agree with @DistributedDoge's comments about tx gas and timestamp

• include passport yes/no and score for voters?? Not sure if this is possible / good idea

[poupou-web3]

Seeing Carl's comment made me think that a table with metadata would be very useful.
Going through the JSON metadata is cumbersome.
I know some fields in the metadata are mandatory and common to all applications, a table for those would be nice.

[ghostffcode]

Pushed an update that includes the Schema feedback provided by @DistributedDoge & @ccerv1 on #11 PR.
Expect this to be merged in the next 24 hours if no issues arise.