Overview

Form a Tableland community team to hack on and submit a project to the hackathon.

https://gitcoin.co/hackathon/DataBuilders/?

Prelim idea

We thought that going after the Data Legos category was pretty interesting. https://gitcoin.co/issue/29676

In this challenge, you will package useful anti-Sybil algorithms into "Legos." These Legos can be thought of as autonomous packaged algorithms that can be run individually in batch mode or tied together with multiple other Legos into pipelines that run closer to real time.

Interesting algorithms to consider packaging into Legos include:

Each Lego should be able to take as input a wallet address (or a list of addresses) and output a boolean response. That boolean response does not necessarily have to be whether or not those wallets are judged to be a Sybil; rather, each Lego could score wallets on a particular attribute, such as whether they have performed a particular set of actions, or if they appear on a given list, or showed certain behaviors.

Team concept

  1. Can we take each lego and track its metadata in a Tableland table, including versioning and other critical information?
  2. Can we then generate validation tools that allow anyone to run a subset of data on each lego and get a predicted result? Something like a test suite.

It may be less of a test suite and more of a record as to what combination of Legos and weights suit the community and their use. For instance use this set of Legos for a vote, and adjust the weights; use this set for a mint and adjust the weights. (See comment above)

  1. Can we generate a pipeline builder, where any user can select the legos from a table, stitch them together and publish a new pipeline for others to use. Mint an nft?

Bonus concepts

  1. Maybe those pipelines should be executed on demand somehow?

Other thoughts

We could probably mock all of the above into a simple UI, set of metadata tables, and pre-canned outputs for demo purposes. This would skip having to actually package or distribute the legos (since other teams may already be working on that, it’s the main callout of the ticket) and instead focus on the pipeline builder and validation tools.

Work areas