At Least 50,000 Sybil Wallets Passed POH – Why Doesn’t Linea Organize a Sybil Hunting Campaign?

Token Design
1

Hello Linea Community,
We are a group of Sybil hunters.

Recently, I noticed discussions in the community about whether the airdrop should be given only to wallets holding more than 1,500 LXP or 2,000 LXP. Or has Linea’s final POH list (February 17) already removed all new and low-activity wallets? Is that truly accurate? In our view, Sybil wallets are wallets owned by the same individual.
The important thing for Linea is that the more real users receive the airdrop, the stronger the Linea community becomes

However, what I want to highlight here is an even more critical issue.

Based on our preliminary analysis, at least 50,000 suspected Sybil wallets have passed Linea’s POH screening on February 17, 2025. (Note: This is just an initial check using duplicate cluster behavior analysis. If we apply additional methods such as fund flow distribution analysis, input duplication tracking, and social footprint analysis, the list could be much longer.)

This list currently includes only clusters with more than 20 wallets, but if we lower the threshold to 10 wallets per cluster, the number would be significantly higher. Below, we have provided a few sample clusters for the community to verify.

Quick Observations from the Sybil Wallet List:

  • More than half of the Sybil clusters hold over 3,000 LXP, with dozens of clusters holding over 6,000 LXP.
  • Many Sybil clusters are not only targeting Linea’s airdrop but also multiple blockchain and dApp airdrops simultaneously.
  • These Sybil clusters are diverse, but clear, undeniable patterns can be found, which anyone can verify.

A Major Sybil Infiltration Will Harm Linea’s Airdrop Event

Allowing such a large number of Sybil wallets to slip through will negatively impact the fairness of Linea’s airdrop. Thus, we propose that Linea organizes a large-scale community-driven Sybil hunting campaign, similar to the successful initiatives by LayerZero and Nansen.

Our Proposal: A Large-Scale Sybil Hunting Campaign

We suggest a three-week public Sybil exposure campaign on the community forum:

  • Week 1: Sybil hunters submit Sybil wallet lists with evidence, and Sybil wallet owners can confess (per cluster).
  • Weeks 1 - 2: Wrongfully accused wallets can appeal and debate with hunters if errors are found.
  • Week 3: Linea finalizes the Sybil list (wallets that do not appeal or lose their debates are confirmed as Sybil).

Benefits of a Sybil Hunting Campaign

  • Eliminate fraudulent wallet clusters, ensuring that genuine users receive the airdrop rewards.
  • Increase visibility and awareness of Linea, attracting more interest from the broader crypto community.
  • Users understand airdrop farming tactics best, so allowing the community to track down Sybil wallets is an effective approach.

Sample Sybil Clusters

Below, we provide a few Sybil clusters for the community to verify. You can check these wallets using Arkham -intel.arkm.com- or any other on-chain analysis tool. These tools will reveal that wallets in each cluster exhibit identical on-chain behaviors, making their Sybil nature undeniable.
Sample Sybil Wallet Clusters:

wallet lxp cluster
0xb42cde5bb7e58b2924370b78b561091287514c23 5575 Cluster01
0x7e8f45b491bb55a6f878f1a60d04f66230daf0bd 5519 Cluster01
0x689ad82a597820b311e76eb4828cf4fdc72dcf4e 5480 Cluster01
0xe45d8852f118f18d97c64676ddaa860b6d5ec94b 5470 Cluster01
0x76670395acefe164ec83dfbe8b2dfa862869b62e 5453 Cluster01
0x0c9ff412450d502f460b6b53c8adc3b1e4eed315 3900 Cluster01
0x0a93f95adbf45c26845c6b1bfd38504611996c26 3871 Cluster01
0xb1f456b114fb13a906095c185c25d6ec7c41ecbe 3861 Cluster01
0x2d15314026a6c24f7ef0c023bc004ba60c30271a 3835 Cluster01
0x88a8c97a06500a64720fcccc5bd452c025f8b1a3 3816 Cluster01
0x58161af380b14707e7f9946a7261fddaf8046cfa 3815 Cluster01
0xee3ea10d010996fe5d14701d8aca4f6241f0c289 3804 Cluster01
0x73d2a1f9a069f375d334e1de77fd3c74bfeee9dc 3780 Cluster01
0xe7aa32ee52020fadd4fba9524b951330f53ac875 3764 Cluster01
0x77bdcef90ad015a18ba564d0311bd731b6ea284a 3755 Cluster01
0x18852add95fe47a5f0d5ea5c7a382e33ebfd602b 3750 Cluster01
0x5fc094b0eff4c7b58635afc08fc9d2aff211e0bd 3746 Cluster01
0x5bcdd1d531f7c23b17a2a1e720ce7acee89f80a0 3740 Cluster01
0xe5bbd5699d8e0cbe761a8dc6374eef297174ad21 3739 Cluster01
0x90a7b1618bbbac12cd9b055df847f8c4511b7b52 3725 Cluster01
0xe6833ea38cccb6ccbd7da51524df2aecf00e3e8c 3724 Cluster01
0x86bcbdabc9bc60bea29ef6c71c677b5ee2793545 3679 Cluster01
0xdb80ae99cbe0f6e1d86cb85d106ecb55769b69f6 3603 Cluster01
wallet lxp cluster
0x568a9af451c61055bf37a9f517918801b0b462f1 5595 Cluster02
0xb0630f84e264b0b726f6d984d2a7c7dbb4ba2cf7 5585 Cluster02
0x36a1ae18e4322aaf1dfdb96c315e5937fb9f1916 5536 Cluster02
0xc0e9a2998baf5c0f8f0022e9e924783737373d04 5536 Cluster02
0x27d5f6e57898d6efaeb263b2015a1883c8aa1dbb 5527 Cluster02
0x805aa091ffd19213827d8022ddc11e47143386b1 5515 Cluster02
0x2f46e63ee58766e99a690657ac7578d476c6249c 5505 Cluster02
0x13f56add2822f1d1523cef43653630a4ff2b1745 5500 Cluster02
0xe06ffaf010801dda1316f372e963309d86e1f603 5496 Cluster02
0x3443efdf0813303e924c03b6da32742c8d79b4f3 5495 Cluster02
0x8ceab102a8275022b99505dd52480412c68b634f 5495 Cluster02
0x88d6c261b081693c384fdaf8f45b62a2edbc4f60 5490 Cluster02
0xeb689b6948373b4e63fe27e7a1d907a786f493dc 5489 Cluster02
0xbb0c0cf04360b003dc8b9bfd44b6d62ce961d671 5467 Cluster02
0xc6b5ededc20a563ec25658e74db89c764758ed41 5466 Cluster02
0x59e9ee99c4e31921cf2a3b2ff44f66388434cc9d 5464 Cluster02
0xe6c3304de3220ef8e3b80d649b70840f2f73052a 5460 Cluster02
0x0e4cfb0db6b548ae8e5882fbed498f605ad24f5f 5445 Cluster02
0x0fa67ddf69d80d768d3e882c7a9672ec556bb362 5440 Cluster02
0x66c6878993924e85bb562794f44f44e6b2612720 5397 Cluster02
0x2f6cbf4fe15540bc01c1fe81dbe20999a3394788 5269 Cluster02
0x34b82644a0a669670aabf67f09c5af087db7ab9f 4805 Cluster02
0x2da74eac1ee6e6e8f36f8f1bd7425a6574414c50 4725 Cluster02
0x3bae7aea69d12127e75d3b2046113943ff572f4b 4705 Cluster02
0xadb11487d2113729087b5800566400f739ea85da 3754 Cluster02
wallet lxp cluster
0x2b2fb6633ec296062b1ad654eb65f775548a7a5d 3885 Cluster03
0xb20b155ca3ab4fd94c92043a0781fb02c55ef998 3875 Cluster03
0xc626086c11442b3997cc748f932ba7fff577975a 3860 Cluster03
0xbd5e0a7e140f09bff863a7b218eac1a1d7029bad 3855 Cluster03
0x88ec1f8b744cf05d67e1aa1ccbab60ce0d6384ab 3850 Cluster03
0x2fedbf1888d2c28a78e6f4a0b416edfb73b6246d 3830 Cluster03
0xdce1aa5caa7602407b5873e3b25fcbe5e526a3b5 3830 Cluster03
0x0bcd6985560317783cd7dfab828deddaa5fe0a2e 3825 Cluster03
0xcb1a84201ef45b772b399f0016f9ba0a3e13547a 3800 Cluster03
0xe4b20b36950e5b75d78964be60a81fc5022e4606 3800 Cluster03
0x363e6b47559930552eccf8404ad9849dd599f744 3794 Cluster03
0x1e624329f42dee8f0703030e4acec57e20ac582d 3785 Cluster03
0xcbd3925e377a50ba03921058fa0e5147c38e0fd4 3780 Cluster03
0xdcc26092857983c747b61b011360c30d5d320305 3780 Cluster03
0x7bd78d0261c0bccd73cb3339fa61dbb21fbcd79d 3775 Cluster03
0x7f9ebec28ff7921257dde47c1196cf1a32452ec4 3775 Cluster03
0x661056bc3b01b6e3b8d4bdc58498870da813b754 3770 Cluster03
0xdb5a30cf0ae6a1498ec7fbf9d6bfd64a46d7f8db 3770 Cluster03
0x6e61b89688647e8359ab19ef22286d334719fd3b 3750 Cluster03
0xe992ad5eb5f6ae59ac7a7d37cd2a4c13635fde24 3735 Cluster03
0x168d57f3a3b88f349520f456b0bf38449e863df4 3710 Cluster03
0x709e343ae2d42cf7c1e76905854da588a3ca6c9a 3705 Cluster03
0xe8fecf811fa724b0ef85e89187886a13dd45b1ff 3700 Cluster03
0xdcf94e00d9976bce6390ae89d711cadd495c4e09 3665 Cluster03
0x1055b28e3eadaf94bb015639a5d10f2bec386461 3655 Cluster03
0xd576eeaafb49a6e9f1a9e0d64a45d0c17320fc09 3655 Cluster03
0xe472ce2dd0dead3b128d4b9b336008f502f60c2a 3655 Cluster03
0x105bd2a6dddd6fa5bf4a77c90c0974ce0c8568b0 3650 Cluster03
0xcffe294cbcbdee2d847da673c8455fd46555956b 3645 Cluster03
0x047e1ebc61aeb3a55e6e3cff9b6ec14f1300820b 3625 Cluster03
0xb80769be49e54d74aaed99a5a79dac32a4045569 3625 Cluster03
0xac35261ec720c98ac05f769f00f259c87cd33f2b 3605 Cluster03
0xdbf39bc58bc9928792e29cf8f984070b9eba723c 3601 Cluster03
0x0946e349db169c031d656d93b4901b878c3ac9f4 3600 Cluster03
wallet lxp cluster
0xc8fe6655f03e0690c08bd14d0823ffd8bf61be3e 5535 Cluster04
0x223ecde889b0fc8a39b998988ce99cb4271947fe 5529 Cluster04
0x059eb1d68e7f22a145bbfe6b436e72fb0f5efc09 5525 Cluster04
0x31b406e20ebc6fa0d720f21c63ebf791d60df119 5519 Cluster04
0x90ec6bc35779509a076571a22a0ae6a83c0de180 5515 Cluster04
0x6cb9511aa2b4ad4064f4617bf343738585eac998 5513 Cluster04
0x6c0a5e7647de20e134d934aad0365cffccd300e8 5484 Cluster04
0x29ec472dc0ad629cac35016dbae1e9989f080ee3 5465 Cluster04
0xc9a351b765eddf3cabafe6819c76340722a28164 5462 Cluster04
0x2b066aa323e7143114845086dd51ed45a13a3281 5457 Cluster04
0x59521e13256517f9b46244813060f28b024c3248 4820 Cluster04
0x0cb6da152d1553ad6d6b5b0a128c6a4572576b45 4820 Cluster04
0x3885721077e7fd4dcb736911a4648e61939d9a88 4807 Cluster04
0x31c8c6fb35142200fc1ee72b8ac37340a4798365 4800 Cluster04
0x807d76ee24f812cccb841d322056d3615d688157 4797 Cluster04
0x3c4467222028c30de695c26eee3e23f83b8e8f96 4794 Cluster04
0x596659ff836adcceff0e3d3373f994c5ca288979 4790 Cluster04
0xe27f5b5bf9aab6f82eaae436aac4a278fcd35a82 4777 Cluster04
0x1049773ba34487eb6addafccd56c3c8013705442 4775 Cluster04
0xea9de62a3cdba9cec372c51f1a0e6805db48cff2 4770 Cluster04
0x82e2aa35e0a8b13d36b910121ee1fa2138d818d9 4769 Cluster04
0xbd7094071386377b4d8406c2136efe6a0f769335 4764 Cluster04
0x602029bccebe1d86dad5f6e60324ad69bf6eb16a 4752 Cluster04
0xac2837f1dd1667e49b82c6b67d11fdc2a00ca2fa 4751 Cluster04
0xc89a85fd17b966bb95ef404f3e4812bf81a51274 4751 Cluster04
0xddbaae32ac994508c069071ddf455d73e72bb4db 4750 Cluster04
0xce07fbb1ed1faeacd667f50482071875ce64bd49 4749 Cluster04
0x2356e125597ba4c77031a4ca9009dc7d73df513e 4749 Cluster04
0x1b8c65eeceb9a7e4fdb4e244ed56887b723e0151 4745 Cluster04
0x578e3f94fc3a9fde6c32e1185d7be2e27d212c9a 4744 Cluster04
0x2690a2897b10b119e693a81dbfe81e8be690467c 4739 Cluster04
0xd8c2273cd9336e877d11aa8b5b9c6d9b0e2ec9d9 4736 Cluster04
0x678625c64f4cc971f83df9d222610aed8ad769de 4729 Cluster04
0xc0919c0953632d060b27d83676847ac07db9a187 4725 Cluster04
0x76e1a3c5078d4a27df70a2490e380d41965c0ca4 4725 Cluster04
0x6669c655349852984e20e728d208b65001510532 4723 Cluster04
0xad1045a631dfb468acc69ae21514f72a50870af2 4719 Cluster04
0x08614c0662a071325b07967f02f68f5ee96cbdcb 4719 Cluster04
0x701bcf8c90bd78aadf338057bcfff7afa21aea4a 4719 Cluster04
0xe67b4950fc15b5d503f8150b2f23b69eaa26c451 4689 Cluster04
0x20c7c32240b6445ffde05a460d23d08a2ad9ffb5 4674 Cluster04
0xe65b3cab849dc8b0d8f9704bcd8d2b6fd7b378ca 4649 Cluster04

Example of arkham analysis data of 2 wallet addresses in the first cluster:

wallet 7
wallet 7954×832 89.1 KB

wallet 11
wallet 11955×821 75.4 KB

11 Likes
3

@dfox @Kanenz

2 Likes
4

It’s important to detect a maximum of sybils accounts ; obviously, it’s impossible to catch all.
But the worst for the project would be to exclude real users because they hold few LXP.
100 users with 1000 $ are as important as 1 user with 100 000 $ !

2 Likes
5

@dfox @Kanenz

Enough is enough.
The Linea team has analyzed sybils (POH) five times over the years. They have made it clear that there will be no Sybil bounty program to avoid a PvP environment. Since launch, the Linea team has focused on building a united community. Additionally, they pinned a message allowing the community to report suspicious addresses before the Final Review deadline.
If your intent is to earn extra airdrop rewards by reporting sybils, the answer is no—there are no tokens to dilute. You had ample time to report sybils before the final analysis. If you weren’t active in the Linea Discord and missed this, or if you deliberately waited in hopes of a reward, that’s on you.
It is impossible to filter out all sybils, and we all know how much chaos and noise a PvP-style sybil bounty program would create. Worse yet, people with zero on-chain activity in Linea could potentially receive rewards, only to dump them at TGE—just as sybils do with airdrops.

Discord Pinned Message:
“Sybil Report Inquiries: For those inquiring about where to report sybil clusters, Nansen and Linea have already done extensive work and are currently reviewing feedback and appeal forms. If you want to report any additional potential clusters, feel free to DM me directly (remember, I will never DM you first). There is no financial incentive for reporting Sybil clusters. Thanks!”

POH Process:
1. Testnet Reward: Gitcoin Passport
2. Mainnet POH:
○ Class A: KYC verification
○ Class B: Two additional verifications
3. POH updates: Three times in 2024
4. Final Sybil Review: Conducted by Linea & Nansen
5. Appeal Form Review

Community almost always doesn’t look at the data closely and claims all wallets as sybils, hoping to increase their own rewards. For instance, when Bryan, the CEO of LayerZero, posted suspicious wallet addresses on Twitter, the community quickly claimed they all are sybils. However, in many cases, project owners responded to his tweets, proving that those wallets were not sybils. Just because on-chain behavior appears clustered doesn’t mean those addresses belong to sybils. Then, the community’s response is, “Okay, what’s next wallets to kill?” If project owners didn’t respond, the wallets were automatically assumed to be sybils.
The community only cares about how much reward they will receive, which is why there has been so much debate over the minimum LXP threshold. Even Bryan acknowledged that there were a decent number of false positives after the ZRO airdrop and admitted that achieving zero false positives is impossible. That is likely why LayerZero’s final sybil list was never released publicly.

Sybil Criteria is Subjective
Different people have different definitions of what constitutes a sybil.
• Case 1: Someone creates 20 accounts, each completing POH verification using family passports. They manually perform all quests on these accounts. Are they a sybil? If so, how can this be proven? (CC2, a well-known crypto influencer, is a good example of this.)
• Case 2: A family of 20 members participates in airdrop farming. They each complete POH with their own passports, share the same source of funds, and perform the same quests. Their on-chain behavior looks identical. Are they sybils? How can this be proven?

Linea and Nansen have not disclosed their exact sybil detection criteria, but they have at least revealed that the maximum wallet count is 20 and that scripted-based behavior was a key factor. It is likely that they also considered KYC and other factors.
I am not against sybil filtering, but as I said—enough is enough. The Linea team has stated that the appeal form review was the final sybil analysis. The community had its chance to report suspicious wallets before the deadline.

Before the final sybil analysis, I personally proposed multiple sybil filtration methods, including ADS-hacked wallets. I am not advocating for sybils—I simply believe it is time to move on. We have spent years discussing sybils, and at this point, it is unproductive.

I trust Linea and Nansen team’s effort to filter out possible sybils. If you don’t trust Linea team, just move on to other projects.

6 Likes
6

@mariejane1190

1. We Cannot Ignore Sybil Attacks, Especially Given the Large Numbers

We cannot simply turn a blind eye to Sybil attacks, especially when the numbers are significant. In just this list of 50,000 wallets alone, approximately 200 million LXP has already been stolen by Sybil attackers.

2. Why Is It Crucial to Organize a Rewarded Sybil Hunting Event Instead of Submitting Free Reports?

Although our software can quickly generate a list of 50,000 Sybil wallets with an accuracy rate that we know is very high (as validated through LayerZero’s event), we cannot simply publish that list here. No matter how accurate the system is, there will always be a small percentage of wallets misidentified. We work very cautiously and will only report clusters when we have thoroughly verified that every wallet within them is indeed Sybil.

To confirm that a cluster of wallets is Sybil, we follow a three-step process:

STEP 1: Collect on-chain data for all wallets.
STEP 2: Run analytical algorithms to automatically filter out suspected Sybil clusters.
STEP 3: Manually verify each cluster using human validation methods or cross-data analysis to ensure that the identified wallets are actually Sybil and not mistakenly flagged legitimate users.

Among these three steps, Step 3—if done manually—yields the highest accuracy with minimal error, but it requires a substantial amount of time and manpower. Imagine you are a superhuman and can check one wallet in just 10 seconds—how long would it take you to verify 50,000 wallets? This is why Sybil hunters deserve fair rewards for their efforts.

Of course, all three steps can be fully automated, similar to how Linea and Nansen approach the problem. However, this would mean reducing the detection sensitivity to avoid false positives, which in turn allows many Sybil clusters to slip through the cracks—such as the 50,000 wallets in this list. Fully automated methods also struggle to capture the most sophisticated fraud behaviors.

Additionally, whether the process is done manually or automatically, Sybil hunters still invest significant effort, making the rewards well-deserved.

3. Why Was LayerZero’s Sybil Hunting Event Somewhat Chaotic?

  • Lack of prior experience: LayerZero was the first project to introduce a Sybil hunting policy, meaning they had no previous experience to build upon. Their initial event was launched on GitHub, but due to technical issues, they had to move it to a forum, causing disruptions and allowing malicious users to interfere. However, we now have the advantage of learning from their experience.
  • Inefficient report handling: LayerZero’s reporting mechanism did not effectively facilitate discussions between reporters and appealers. As a result, they spent a lot of time verifying results. This issue can be addressed, and we have proposed a solution in this proposal. By implementing the principle that if one wallet in a cluster is successfully appealed, the entire cluster is removed, we can ensure that Sybil hunters thoroughly verify every wallet in each cluster. This would significantly reduce the workload for the Linea team.
  • Technical support: If Linea requires assistance, our team can provide a Sybil hunting event reporting software within one week, capable of handling all Linea’s Discord users participating simultaneously.

4. Was LayerZero’s Previous Sybil Hunting Campaign Successful?

  • LayerZero’s Sybil list is highly reputable and has been widely used by other projects, including ours.
  • There was significant community engagement around LayerZero’s Sybil hunting event.
  • The community did not strongly oppose LayerZero’s final airdrop list.
  • ZRO was a highly successful token launch—not only did its price not drop after the airdrop, but it continued to increase for months afterward.

Based on these points, we see no reason not to organize a Sybil hunting campaign—especially when we know for certain that many Sybil wallets are still out there.

3 Likes
8

Another guy coming from nowhere with his team to collect money from reports, destroy community and quit, leaving exhausted community with endless PvP after hundreds of check-ups, sybil lists, PoH processes, delayed TGE with still unknown date, possible threshold on LXP and still many things undisclosed till today.

I think a sane guy, even if he wanted to make money with his noname team, without a company with a long history that Linea could turn to for help, would have come here before the final Sybil list, at least before the appeals.

That’s enough for the community. I really appreciate your desire to make money for finding some inefficiencies, but I guess your timing is just bad, buddy. That’s enough for the community, too many delays and endless processes with a phantom desire to choose the best possible scenario. There is nothing completely ‘ideal’ and ‘pure’ in this world. You either perform or wait for a better moment that never comes, same goes for endless Sybil investigations.

I strongly disapprove of all these Sybil bounty programs. It’s always a PvP environment filled with people from different blockchains who didn’t care about Linea before the bounty program. All those sybil investigation processess must be handled by independet company with high expertise and large professional history, not by a bunch of random guys coming to earn their fee from every reported person as in any affiliate program.

3 Likes
9

Sybil farming is when all transactions, dates, amounts, and other parameters match exactly 1-to-1 .

Your statement is incorrect. Sybil does not necessarily mean that all transactions are identical. As long as it can be proven that the wallets belong to the same person, it is considered Sybil. The fact that wallet addresses have identical transactions on a one-to-one basis is just one condition to confirm that they belong to the same person.

I checked the wallets from the first batch that you marked as a cluster. This doesn’t qualify as Sybil. Just open Debank and compare the transactions across all the wallets you listed—the transactions are different.

Moreover, if you didn’t know, most people follow ready-made guides from influencers to complete tasks, which increases the appearance of Sybil-like behavior from the outside—but even that isn’t the case here

Talking about Sybil cluster #1—if you see any addresses that do not belong to this group, please point them out, and I will provide additional evidence to prove that they indeed belong to the same individual. Besides transaction timing evidence, during the Linea Park event, many dApps caused scripts to run automatically, exposing cluster information in transaction parameters. This cluster #1 might be even larger in size.

It seems like you are trying to justify this wallet cluster, but that is not accurate. Try checking the first two wallet addresses in cluster #1. Their first transactions occurred on August 24, 2022, just 50 seconds apart, with the same amount. A few minutes later, they simultaneously purchased Arbitrum Odyssey NFTs through tofuNFT, then remained inactive until September 5, 2022, when they reactivated and once again executed transactions with Odos at nearly the same time, with the same volume. Over the next three years, these wallets consistently executed identical transactions. Even highly unusual transactions—such as when these wallets farmed volume to hunt for zkSync rewards—were carried out in exactly the same manner, with the same abnormal volumes, at consecutive timestamps.

What kind of coincidence leads to identical behavior over three years across 23 individuals? Were they following a specific guide? Or were they fans of a particular KOL?

We analyze on-chain wallet data across all blockchains, not just within the context of the Linea event, so our behavioral data is highly accurate.

1 Like
10

I understand your concern but it seems that with the current situation, the information about TGE in Q1 has been removed, so the TGE event will probably take place in a few months. What do we do in the meantime?

1 Like
12

It was said many times, the sybil list is final with no further additions. The last thing the team is working on is criteria, everything else has already been finalized. I guess there’s no logic in those endless sybil hunting processes. By chasing this you’ll never get the final list of people to play with criteria.

You could come here way earlier, before final sybil list or appeals. Now the best you can do is to help with criteria, not creating this PvP environment to destroy the rest of the loyal community.

There are plenty of things the team can do during this time gap before TGE. Sybil list is the previous step before introducing criteria and releasing checker. If you endlessly run those sybil investogation there won’t be any time when you release the checker with criteria.

Sybil reports are in the past, sorry. We’re moving forward towards criteria and tokenomics, not backwards with new appeals, delays etc.

2 Likes
14

where u are in last 6months and what your doing when Linea team suggested to report suspicious wallets/clusters. Just for bounty rewards ur suggesting now why u did not propose/suggest earlier. What do think about Linea team they have nothing to do except sybil hunt or what

15

People like this guy do not care about Linea.

The most important factors for public blockchain are decentralization and community. PvP environment always destroy community. Although TGE is delayed, this is the time to set united one community.

Moreover, Linea team officially announced two things. There will not be any additional LXP and LXP-L related quests. Moreover, there will be no additional sybil update.

You had enough time to report and suggest it before final sybil report. In my eyes, you act is same as sybil. Simply, you want to have more airdrop than others and don’t care about Linea’s long term thrive.

If you are true Linea believer, trust Linea team. As above person mentioned, there have been multiple POH update and I trust Linea team.

It is time to move on to Tokenomics and airdrop criteria, not endless and repeative sybil things.

2 Likes
16

Absolutely!
@king_of_kingsh

17

How long do we have to keep talking about sybils…
It is really tired to see if there is still person who keep screaming about sybils.
Linea team already did sybil analysis for years. It is time to move on.
If you don’t trust Linea team, you better move on to other projects.
I used to be one who shout out all sybil killing but I have not claimed any more sybil filter after final list. You don’t deserve this project.

18

If you really want to contribute to the project, you should discuss how to continue the project instead of just pushing the TGE project. Many projects are forgotten after TGE. PvP is fine. The more active the community is, the better for a Blockchain project. Projects that airdrop all tokens to a group of sybils (like Zk) and then dump them causing the price to fall without bottom are the ones to worry about.

19

In my eyes, you are the second account of author “goldencat”. Stop playing.

Evidence:

  • Newly created account
  • Identical claim
  • All post and comments are simply sybil hunt only (your profile shows history only 2 activity)
  • Supporting PvP is fine

I saw people like you in other project as well. All caring about is simply collecting more reward and move to other projects and don’t care about long-term project survive. Linea team has done sybil hunting for years and Nansen also collaborated with Linea team. If you don’t trust Linea team’s skill, you better find other projects. There is no room for anti-community members on Linea blockchain.

Remember, community had more than enough time to report suspicious wallets. It is obvious that small group of people would like to make noise and harm community

Two harmful groups

  • ADS hacked wallet users pressing Linea team to find other way to reward them
  • Ridiculous endless sybil hunt bounty program even though Linea team said final report is final.
1 Like
20

@mariejane1190
And me too.
We’ve been claiming our status as a hunting team since our first post.

21

Guys, it is time to move on. We have already wasted too much time and resource for sybils. If the topic and priority were on developing the project, I am certain that we did TGE much faster. Everything is vague now and unclear. Community has already started losing hope and trust on Linea project. Yes, there are still few people supporting Linea but Linea needs to be broad adoption, not only for Linea cult users.

1 Like
22

holy shit this needs to be addressed officially

23

Skimmed the cluster and not clear evidence with less than 20 wallets.

Final sybil analysis is final. Please follow the Official announcement.

No more delay for any other action than TGE.

No more ADS hacked user to claim re-analysis as well.

24

This Sybil hunting campaign is nothing more than a flimsy, overblown distraction a theatrical farce that masks real issues with baseless finger-pointing. Instead of channeling energy into meaningful, constructive progress, the focus has shifted to a petty witch hunt that inflames unnecessary drama, while now some players are clearly trying to game the system to farm rewards rather than address genuine challenges. It’s a cynical maneuver that undercuts the integrity of the process, and honestly, enough is enough.