Community Whitelisting for Synapse Network
KYC Selection Process (Early Stage Community Round)
We received a total of 54015 responses in the Synapse Network Early Stage Community Round. The number of whitelisted spots available is only 200 in total for this round and meant that only a small percentage of those who applied could be whitelisted. To present a detailed process of selection, our team followed a structured approach based on the conditions listed below. We are also sharing the entire data as well as the code so you can verify the authenticity of our selection procedure yourself.
All 500 whitelisted people will receive an email confirmation shortly.
STEP 1 GLEAM DATA ANALYTICS — FRAUDULENT AND SUSPICIOUS ACTIONS REVIEW
Firstly we used the Gleam platform data analytics to mark every suspicious entry. After that, we analyzed every entry to find connections between entries and ref-links, IP addresses, locations, time of filling etc. We supplemented the analytical data with the manual analysis of the report — this allowed us to find even more fraudulent entries. The country with the most fake entries was Vietnam.
Gleam Analytics:
total entries: 274860
total actions: 54015
total users: 5999
Invalid actions found by Gleam: 926
Removed accounts: 149
Multiple reflink frauds: 11
Fake Twitter accounts (multi-accounts): 19
Fake reflinks : 5
No wallet: 23
Duplicate entry: 41
Fake identity (multi-accounts): 50
After Gleam Review:
total points: 248635
total actions: 51383 (2632 invalid or fake actions has been removed)
total users: 5850
STEP 2 DUPLICATES REVIEW
Using our own tools and manual data analysis we were able to review the applications again to delete additional duplicates, banned countries or incomplete data.
total entries: 236690
total actions: 51383 (11945 invalid or fake actions has been removed)
total users: 4605
STEP 3 SPREADSHEET CREATION
After clearing the duplicates, wrong countries, and other incorrect data, we created a CSV file including all the correct entries. We are preparing the spreadsheet that will contain three columns: a) assigned number, b) ERC20WalletAddress and c) total points assigned for entries. For every Gleam entry we are assigning a consecutive number to a wallet. So for 50 entries, a user (and his wallet) will have 50 numbers assigned.
You can find a table under the link below:
https://drive.google.com/file/d/1sshLUjPSUUK3zeTd39Grnp4FG7bExJrO/view?usp=sharing
STEP 4 PUBLIC HASH
For the avoidance of any doubt, we will publish the SHA256 online hash file checksum function. Anyone will be able to check the hash value — this proves that the data has not been tampered with.
SHA256: 5821701B92888817D5E105AA5BAC3A2B6F5E4FFC486BB6960EEA739B427B9D8B
You can check it by yourself, for example using powershell, or any other SHA256 :
Get-FileHash .\fileName.csv -Algorithm SHA256 |Format-List
STEP 5 GITHUB.
Moreover, we have decided that on-chain selection is the best as source of proof for the fairness of the selection. We created a whitelist selection contract that is available to check on our Github repository under this link:
The contract was deployed to the Polygon mainnet, verified and now available to check under this link:
https://polygonscan.com/address/0x618817b07eaf4817c9515570659c76296ac15195
The contract is keeping a link to the Google file with data included in the CSV file as well as it contains a SHA256 hash of the CSV file.
https://polygonscan.com/tx/0xda0c47309493ef606929015605ad9574d151b38216fdc1704849579072f55708
STEP 6 HOW DOES THE SMART CONTRACT WORK?
- The contract asked Chainlink for a randomValue
- Based on randomValue, x unique numbers in the range from 0-to-n were generated
Where each new unique number was also a new randomValue for the function, and n was the number of tickets 236690.
winnerSeed = uint256(keccak256(abi.encodePacked(previousWinnerSeed, i, nonce)));
winnerIndex = winnerSeed % ticketsCount;
https://docs.chain.link/docs/get-a-random-number/
Using the contract we firstly selected 600 random numbers matching the numbers from the CSV file. Everything can be verified on-chain. We selected more numbers than the required 500 participants because there have been duplicates (one wallet can be selected many times). In the end, the first 500 unique wallets were selected.
Transaction TX:
A CSV file with KYC winners is published here:
https://drive.google.com/file/d/1VRME3NHDDAGTp2p3WGkfS8PASwYAokyE/view?usp=sharing
SHA256: 9880D077301AB4F30765E3277A91E3CEC78B202794541DCC6A5429F425B12911
STEP 7 REGISTRATION
The next step for all KYC winners is registration on the https://app.synapse.network
You need to use the ERC20 wallet that was published in the CSV file.
The required step is performing the KYC (with wallet check). Please select ERC20 wallet, not BTC wallet and use the same wallet as was published in the CSV file.
STEP 8 FINAL DRAW
- People who will pass the registration and KYC will be added to the new CSV file — every wallet is going to get assigned to a single consecutive number.
- In order to avoid any doubt, we will post to the public a sha256 hash of the file. Everyone will be able to check the value of the hash — this will prove that the data was not tampered with.
- The contract will contain a SHA256 hash of the CSV file.
- The contract will select 200 random numbers matching the numbers from Spreadsheet. Everything will be verifiable on-chain. We will explain the way for everyone to check the results. These people will be in the main group of investors. The other 300 people will remain on the backup list in a randomly ordered queue. These people will get an investment opportunity if the investors from the randomly selected group of 200 people fail to invest.
Thank you for participating in the Early Stage Community Round, we will soon announce the next investment rounds in which you will be able to participate. Stay tuned!
The future is decentralized. The future is here. Synapse Network — one place to rule them all.
Website
Twitter
Telegram Announcement Channel
Telegram Global Group
Github
Youtube
Linkedin
