header-langage
简体中文
繁體中文
English
Scan to Download the APP
Partnered With:

Those "hard indicators" for Identifying Boca's Real and Fake Projects (PART 1)

Read this article in 10 Minutes
To help you identify the real and fake "Boca Ecological project" some judgment methods.
How to Study Real Polkadot Ecological Projects? Check out official advice!
原文来源:PolkaWorld


Many projects are being built or planned on Polkadot and Kusama. However, some people just say,Will not beIt's probably because he doesn't have the resources to do it, or they just want to do it by abusing the Polkadot and Kusama brandscheatingThe community.

 

It is not always easy to tell the real Boca Eco-project from the fake. This guide is designed to help you research a seemingly good project when you come across it. Note that this is not telling you whether a project is a "legitimate project" or making a decision for you.

 

In addition, a legitimate project does not necessarily mean that it will also be a successful project, this guideShould not be taken as financial or investment advice.

The first part of the guide, which Outlines some "hard metrics" for identifying fake projects, will be published soon.

 

Note the "supported by Polkadot" or "Polka" prefix


The "supported by Polkadot" statement on many project websites is often confusing. This usually means that the project is or intends to build on the Polkadot ecosystem using Substrate. But any project can make this claim, so it exists on the project websiteDoes not mean thatThe legality of the project, of courseNor is it the "seal of approval" of the Web3 foundation. .

 

The same is true for projects with a "Polka" prefix in their name. Many projects use it to associate themselves with Boca Ecology, some legally, others just to rub off on Polkadot's brand.


Some hard targets that must be met


1. Associate with or partner with an entity you trust


New projects often attempt to enhance their credibility by associating themselves with well-known entities. The idea is simple: "These reputable entities trust us, so if you trust them, you should trust us". In fact, an association with a trusted entity can become project legitimateStrong indicators.

 

For example, if a project is awarded  Web3 Foundation GrantWhich shows that the project is indeed built on the Polkadot ecosystem if they havedeliveryWith all the milestones, their code is likely to be of reasonable quality.

 

The Web3 Foundation is not the only entity in the ecosystem that offers grants. There are other reputable teams in the ecosystem that have developed platforms or parallel chains and funded their ecology projects to build or expand their ecology. These are also reference indicators for a legitimate project aimed at building on the broader Polkadot ecosystem.

 

Or getting funding from a venture capital firm you trust and being known to be involved in other well-known Polkadot projects are also good indicators. Or participate in & have spentSubstrate Builders Program  The project.

 

But claiming such collaborations is not always the same as owning them. You always needvalidationItems are presented in any statement that may be in this guideThe most importantThe content of the.

 

For example, if a project has a Web3 Foundation Grant badge on its website or claims to have received a Grant, check to see if they have received a Grant and have been terminated. Can be found here (https://github.com/w3f/General-Grants-Program/blob/master/grants/accepted_grant_applications.md) has been successfully to apply for a grant You can also see what each project has delivered and whether their funding has been terminated here.

 

Similarly, this applies to venture capital funding or other grants. Check the appropriate website to ensure that such claims are valid.

 

In addition, you need to understandScope of cooperation. Going back to the Web3 Grant example, it has precise scope. Funded projects need to have deliverables, and the review team only examines the code and evaluates specific deliverables for those projects.Therefore, receiving a Web3 grant does not imply an endorsement of the team's general practices, project life, or other projects the team is building. This is why we have repeatedly made it clear that the Web3 Grant badge should not be displayed on the team's landing page.

 

Similarly, if a project claims to be working with a reputable entity, verify the scope of the partnership and whether it is indeed a partnership by searching their website for projects they are working with, by contacting them directly in press releases. If you see a Web3 Foundation statement like this on any project site, you can be sure that this is false,Because & have spent The Web3 Foundation does not collaborate with or "endorse" ecosystem projects.

 

2. Open source


Open source projects can increase transparency, build trust, and ensure that project teams don't do dubious things behind their backs. In addition, it makes it very easy to track project progress and see how active the team is during development.

 

However, this does not mean that any closed source project is illegal, or that the team behind it has something to hide. Many teams choose to keep their code secret to protect their intellectual property. Some teams that do this also receive our General Grant, and members of the Grant review group review their private code.

 

Another thing open source projects allow you to check is whether they copy code from other open source projects. This is not necessarily a bad thing, as it may avoid the duplication of the wheel, but the duplicated code should be attributed to the source code. Without attribution source code, this should cause some bad things,Because the project team may be copying someone else's code to disguise their own technical capabilities.

 

A forked REPO is easy to spot because it points to the original REPO, but partially copied code may not be so easy to find. This tool (https://duckduckgo.com/?q=search+for+copied+source+code+plagiarism& t=ffab& Ia = Web) can help find ways to plagiarize.

 

Therefore, a closed source project is not necessarily a red flag, it just limits the ability to validate this aspect of the project. However,An open source project is certainly a good and strong indicator of its legitimacyBecause dark and bad ideas are hard to hide for long in open source code.

 

3. Code activity

 

If a project team is constantly updating their product, it is a good sign that they are serious and passionate about development. Regularly releasing new features and updates, fixing bugs, updating their website and notifying the community of those changes is a good sign of a legitimate project.

 

In addition, active development often means good development capability for closed source projects. Of course, open source projects provide the ability to monitor development activities directly through their GitHub repositories.

 

4. Solid documentation

 

For any project you want to take seriously,It should be mandatory to build a solid document. A few years ago, this meant a white paper, but now we're seeing it move into other forms of documentation, such as wiki pages that describe various aspects.

 

Whatever the form of the document, it needs to exist, and the more detailed the better. This is where the project is explained in detail, where potential investors and users can read about how it works, its goals, and how the team achieves those goals.

 

This document will also give you an idea of the team's technical expertise. If they have documentation on analytical techniques, they know what they are doing. On the other hand, if they focus solely on tokenomics or analyze their project only in broad, vague terms, it may indicate that they don't have a clear path to achieving their goals.

 

If you want to reference outstanding document sample, please check our own wiki at https://wiki.polkadot.network/. Of course, you shouldn't expect to find such extensive documentation in a newly launched project. After all, our wiki covers the entire ecosystem and has been maintained and supplemented over the years, and it is still being updated all the time. But this is a good example of how a good project should emphasize what and how documentation works.

 

5. A reputable team

 

Some teams prominently feature their team members on their websites, along with their social media profiles (usually LinkedIn) and GitHub accounts, for development team members to use. This enables potential users and investors to verify the team's credentials, track record, and expertise.

 

But the key word here is verification! Don't take what you see on a project team at face value. Look them up and verify their records. Do a Google search for the mentioned team members. If it's empty, or the only result is about the project, it shows that their team members are fake. The photos on their website (if any) may also be fake. These are usually easy to identify, but if you want to look thoroughly, here's a guide on how to do a reverse image search. https://helpdeskgeek.com/how-to/free-reverse-image-search-tools/

 

In other cases, some developers prefer to remain anonymous, use pseudonyms, or not mention team members at all. That's not necessarily a bad thing. Maybe the team is a strong supporter of privacy, or they want their work to represent their opinions and attitudes. Still, you should try to find out who's behind the project and what they're doing. For developers, their Github activity may be more important. Other team members may be heavily involved in their community, providing guidance and answers, which is always a good sign.

 

However, if the team is not present anywhere and only interacts with the community through agents, then this can be a red flag and you should be suspicious.

 

In addition to their community, serious Polkadot based projects often interact with the broader Polkadot community. They are active in various Polkadot and Kusama channels, and some of them are Polkadot ambassadors or important members of the ecosystem.

 

6. Clear integration relationship with Polkadot

 

There are many ways to build projects on Polkadot and Kusama. Perhaps the most immediate goal is to becomeParallel to the chain. Some of the most well-known Polkadot ecological projects are already parallel chains on Kusama or are preparing to become parallel chains, and most of them will also become parallel chains on Polkadot when they come online.

 

Of course, not all ecological projects are guaranteed parallel chain slots on either Kusama or Polkadot network, all projects need to auction to win a parallel chain slot.

 

By visiting the parallel link page at polkadot.js.org/apps, you canQuickly validate  What current projects on Kusama are parallel chains? On the parallel Threads page, you can see which projects are preparing to apply for parallel chain slots, the Auction page shows which projects are bidding for the next slot, and the CrowdLoan page shows which projects are collecting funds from their community to participate in the Auction.

 

butIs notallAll projects using Substrate to construct chains aim to be parallel chains. Some teams use it simply because its infrastructure can be used to build their custom chains, without any plans to connect to the relay chain. Other projects may aim to be parallel chains on Kusama or Polkadot.

 

However,Building a potential parallel chain is not the only way to build and extend Polkadot's ecosystem.The goal of a project might be to build a DeFi platform on a parallel chain, publish stablecoin or other tokens on Statemint, build a decentralized exchange or any other dApp one might think of without touching the relay chain. That's the beauty of Polkadot!

 

But in all of these cases, their plans for building on Polkadot, whatever they are, should be clearly stated on their website and documentation. Most importantly, though, you should look for an explanation of how they plan to achieve this integration.  If there are no clear steps to get there, just a roadmap that puts integration at some point in the future, that means almost nothing.These should be evaluated alongside your research into the technical capabilities of the team.

 

This is especially true for projects that are already running on another network, such as ethereum or binance smart chains, and have issued tokens there. Many projects do this either to raise money and test their infrastructure, or because they aim to build "multi-chain" solutions, or both. However, since these projects are not currently based on Substrate, in the course of your research,It is essential that they have a clear plan for integration with Polkadot, ensuring that they are actually built on Polkadot.


The original link


Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia

举报 Correction/Report
Choose Library
Add Library
Cancel
Finish
Add Library
Visible to myself only
Public
Save
Correction/Report
Submit