The deadline to self-report as sybil has passed. The publication of the initial list of addresses that are not eligible for bounty hunting can be found here.
Successful reports result in the sybil addresses receiving nothing and the bounty hunter receiving 10% of the sybil’s intended allocation.
Bounty hunters can use the information below to produce a report; however, submissions after the deadline will not be considered.
All transaction data prior to Snapshot #1 can be downloaded from Dropbox and AWS S3. The data is provided in two formats, one single csv file and a tar file that is split into smaller chunks.
Use the Issue Template within this Repository to provide the following:
Provide a list of LayerZero sybil addresses that would currently receive a token allocation and are not on the lists published by LayerZero, Nansen, and Chaos (which includes self-reported addresses). If your report exceeds the issue character limit, you can add comments with the additional addresses directly to the issue. Avoid using external files.
Describe in detail the relationship between LayerZero addresses suspected of sybil. The goal is to determine how these addresses are linked to each other and/or linked to sybil activity.
Explain the method used to identify the addresses and provide proof that they are all controlled by a single individual or entity. The methodology should be easily verifiable, and have a low risk of misclassifying real users, otherwise the report will be deemed ineligible. You can report multiple sybil clusters in a single issue, provided that the same methodology applies to all accounts listed. Include references to any additional materials within the issue.
Please provide an Ethereum address that will receive any potential rewards earned from this submission. Note: this cannot be claimed until TGE. All allocation eligibility will be subject to any legal or geographic requirements.
This framework is inspired by previous work done by Safe and Hop.