Factory Guide: Create a Data Group in 5 Minutes
- Web2 Data Sources: Twitter, GitHub, Telegram
- Web3 Data Sources: Ethereum addresses, ENS, Lens handles
Here's an example of what a Group looks like:
// Sismo Community Group made of multiple types of accounts
// full group: https://sismo-prod-hub-data.s3.eu-west-1.amazonaws.com/group-snapshot-store/0xd630aa769278cacde879c5c0fe5d203c/1687260637.json
Here is an instance of a Sismo Connect App that has been implemented using the proof-of-humanity Group:
Sismo Connect App example
This Sismo Connect App allows you to gate contents/features of your app to Proof of Humanity registrants without revealing the registered addresses.
In this tutorial, we will create a group composed of:
- Sismo Lens Followers 🌿
- Sismo EthCC Booth attendees 💜
- Sismo contributor Level 3 🔨
- Some Sismo core team members 🎭
Next, you will have to sign in to the factory with your Ethereum address. To do this click on the login button at the top left corner and sign the message.
Once you are logged in, click on Create new Data Group (red box):
Factory - Group page
Let's build our Group now 🧑💻
First, you need to define a name for your Group: in our case, we will take the name "sismo-supporters"
After doing so, it is possible to add accounts using three different methods:
Data sources fetching methods
There are 3 different ways to define the data of a Group Generator, you can use:
For our case we need 3 main things:
- Define the Sismo core team members
To do this, go to the "By uploading a list of accounts" section, and put your list of Data Source.
Here are the different formats of Data Sources you can use:
- Ethereum addresses (e.g.
- ENS (e.g.
- Lens handles (e.g.
- GitHub accounts (e.g.
- Twitter accounts (e.g.
- Telegram accounts (e.g.
Here we will add some of the Sismo core team members:
List of Data Source
Here we can see that the 7 accounts have been found (blue box). Then click on the Add button (red box) in order to add these accounts to the group.
If you need to import a huge number of Data Sources, you can also directly import them through a json file by clicking on Replace json button (green box)
For our case, we didn't specify the value of each account, so they will all have a value of 1. But you can define the value you want for each account if desired.
For example, different values can be used for voting power:
You need to enter the Lens profile we want to fetch the followers from (sismo.lens) as argument.
Next, by clicking on the Add button (red box), you will know if the Lens profile exists and how many followers they have.
After this, you can click on the second Add button (red box) in order to add these Lens accounts (sismo.lens followers) to the group.
To get the holders of this POAP, we will use the Poap Provider:
With the same logic as before, by clicking on the Add button, we will add the holders of the POAP to the list of Data Sources.
Import a group
So you can select it and click on the Add button.
Finally, that is what you should get at the end:
We will have a total of 15750 accounts in our group (blue box), however, this number will have increased since the creation of this tutorial.
After finalizing our list of Data Source, we can select how often this group is updated. For our Sismo Supporter Group, we select ‘Weekly’ from the drop-down menu. This means that users who become a Sismo Contributor level 3 or follow Sismo on Lens after our Group is created can still become eligible after the weekly update.
Next, you will have to add 2 descriptions:
- a one-line description that explains briefly what your Group is composed of
- a technical description that lists the different requirements for a data source to be part of the Group
Before deploying your group, please be sure to:
- Have texts written in the English language
- Not have obscene content
- Not impersonate others or have otherwise malicious intent
After having completed the captcha, click on the "Request to deploy":
Deploy the group
wainting for approval
We can see that now your Group request is in waiting for approval (red box) and a few time after in Deploying.
If you Group consist of more than 100k accounts then the Sismo Team will have to approve the Group before deploying it. So don't hesitate to send your PR there as well, we will quickly review and merge it (usually under 30 minutes). During hackathons, we are committed to quickly reviewing any new Data Group pull request.
So a few time after your Group will be in deployment and it will be displayed as ✔ Deployed.
You can also click on the 🔽 icon in order to display more information on your group, including the GitHub Pull Request associated with your Group creation.