Very true. This is where the sybil scoring legos we are building with FDD will come into play. Think of each individual analysis as having a boolean output. The exploratory analysis of these has primarily been done and funded by FDD/Gitcoin in the past. Now we have built up the Open Data Community to split this cost with other orgs. Our hackathon in October was 100% Gitcoin funded prizes. The upcoming one in January is 39% Gitcoin funded!
We also clarified the specifications to include containerization and a boolean output. For more on the anti-sybil legos see the articles here.
When you envision this productized where the interface for a fraud analyst or round operator can utilize the many legos beneath the surface, here are a few ways to think of it:
- As a fraud analyst, I want to be able to suggest wallet/passport/grant and see how it relates to it’s relevant sybil analysis legos.
- As a fraud analyst, I want to be able to upload a list of wallets/passports/grants and get an output with the rows being the identifier and the columns being the boolean output of each lego.
- As a fraud analyst, I want to be able to select which analysis legos are executed for my list to save on computation costs.
We have a much more detailed article coming out this week really sharing the vision along with the start of the hackathon which have rewards for both the exploratory analysis discovering new analysis legos and the building of legos, contanerization/standardization of known analysis.