Lens: Web3 score script

User Story:

As a representative of Lens Protocol, I want an efficient script to score the 500,000 addresses on my waitlist, So I can prioritize, filter, and determine the most suitable candidates for acceptance.

Acceptance Criteria

GIVEN I execute the [ScriptName] script, WHEN I input the list of 500,000 Ethereum Addresses, THEN I should receive a comprehensive score for each address detailing the user's credentials.

If the user possesses a Passport, the script should return the Passport score and clearly indicate its Passport origin.
If the user lacks a Passport, the script should execute a 1-click verification process, subsequently returning a potential 'web3' score based on qualifying credentials.
For all users, including those with a Passport, the script should consider factoring in the web3 scorer to ensure capturing all credentials and not missing out on any potential data points.

The returned data for each address should encompass:

ScoreType: Distinguishing between Passport and web3.
Score: The actual numerical score.
GTC Staked: Amount of GTC staked by the user.
Additional Criteria: Any other pertinent data we deem necessary.

Product & Design Links:

Tech Details:

Open Questions:

How should the script output the results? (e.g., CSV, JSON, database entry)
Should the script provide a summary or aggregation of the results?
Can our infrastructure handle processing 500k addresses in a reasonable timeframe?
In the future, should we integrate 'known Sybil lists' immediately, or envision it as a phased inclusion to be added later?

Notes/Assumptions:

The primary objective is to ensure a seamless and efficient scoring process, catering to the vast number of addresses without compromising accuracy. Incorporating feedback, we aim to provide a holistic view of each user's credentials, ensuring no data points are overlooked.

passportxyz / passport