[SPIKE] On-chain Passport Scoring and Data Structure for Attestations

[erichfi]

Goal: To understand the requirements and technical specifications for structuring data in the attestations for on-chain Passport scoring, including deduplication, weighted scoring, and gating access to smart contracts.

Acceptance Criteria:

• Understand the current data structure for attestations in the AttestationStation smart contract, as outlined in the technical documentation provided
• Determine a schema for structuring the data in the key and val fields of the attestations to facilitate on-chain Passport scoring
• Outline the necessary steps for implementing the schema in the smart contract and the potential challenges or limitations

Link to Technical documentation: https://community.optimism.io/docs/governance/attestation-station/

[nutrina]

Copying over my comment from #813:

Regarding the data structure of the attestation station: https://community.optimism.io/docs/governance/attestation-station/#state

To my understanding the mapping could be as follows:

A. creator (gitcoin smart contract) => about (passport owner) => stamp key (Twitter|TwitterFollowerGT100|TwitterFollowerGT500| ... => val (bytes)

or it could be like:

B. creator (gitcoin smart contract) => about (passport owner) => stamp key (hash) => val (Twitter|TwitterFollowerGT100|TwitterFollowerGT500| ....)

Option A would allow an easy check to see if a user owns a given stamp or not. But it make deduplication hard. On the other hand maybe we do not need deduplication at this level, and this would be done in the Scorer ....