Security filters

Security Score

The Blokiments security score is designed to assess the risk associated with investing in a particular token. The score evaluates various security factors, such as the potential for scams, token contract behavior, and other warning signals provided by multiple security providers. Each token is analyzed based on a set of checks, and the score dynamically adjusts based on the findings.

The score's calculation is not revealed in detail to avoid giving scammers insight into the mechanisms they could exploit. If we provide too much detail about the specific checks or thresholds, malicious actors might manipulate their tokens to bypass the system and appear safer than they are.

All detected scams are automatically removed from the filtering results in the Discovery Hub (we are doing our best to remove as many scams as possible, but it is never possible to remove all, so doing your own research is always important before buying a token).

Key Factors Assessed:

  • Contract Verification

  • Honeypot Detection

  • Tax Structure

  • Ownership Renouncement

  • Token Deployer History: The deployer’s history is assessed, including whether the deployer has created numerous tokens.

  • Minting and Proxy Contracts

  • Deployer’s Scam History: The system checks for historical scam reports linked to the deployer or associated addresses. If found, the token is marked with a severe warning.

  • Creation Timestamp: Newly created tokens are more prone to scams.

  • External Scanners and Security Reviews: The score integrates data from third-party security providers

The score reflects the available data and the checks performed during analysis, but it may not account for all potential risks, especially in rapidly changing or highly sophisticated scenarios. Scammers may also find new ways to bypass certain detection methods, and as a result, the security score might occasionally fail to identify every threat or flag token incorrectly.

The security score system uses a simple rating scale to help users quickly understand the risk level associated with a token. The scale ranges from 1 (Terrible) to 5 (Excellent), providing a clear overview of the token's safety based on several risk factors. Here's a breakdown of each category:

  1. TERRIBLE (1):

    • Tokens in this category are highly risky and are often identified as scams or major threats. They may exhibit multiple red flags, such as unverified contracts, honeypot behavior, high trading taxes, or repeated scam activity. Users are strongly advised to avoid interacting with these tokens.

  2. BAD (2):

    • Tokens classified as "Bad" are highly suspicious, with several potential risk indicators. While not confirmed as outright scams, they display characteristics that raise serious concerns. Extreme caution is recommended.

  3. MEDIOCRE (3):

    • These tokens fall into a gray area where some risk factors are present but may not be immediately harmful. Users should be cautious but not necessarily avoid them outright.

  4. GOOD (4):

    • Tokens rated as "Good" show positive security signals. They are verified, exhibit no major red flags, and operate as expected. However, minor concerns, such as certain risky functions or relatively short trading history, may warrant attention.

  5. EXCELLENT (5):

    • These tokens are considered secure, with all checks returning favorable results. However, even with an excellent security score, checking other data like liquidity, trading activity, and socials is always important.

Is contract verified

Ownership Renounced

Number of Tokens Created by Deployer

The "Number of Tokens Created by Deployer" filter tracks the total number of tokens created by the same deployer address (the wallet or smart contract that originally launched the token). This metric provides insights into the deployer’s activity, revealing whether they are focused on a single project or involved in multiple token launches.

Why It's Cool: This filter helps you assess the credibility and intent behind a project by examining the deployer’s past behavior. If the deployer has created multiple tokens, it can be a sign of a prolific developer or team, but it can also raise red flags about the potential for scams, such as pump-and-dump schemes or rug pulls. Understanding the deployer's history allows for better risk assessment when evaluating a new token.

Some apps can easily deploy tokens using the same deployer address, even if the token owners are not connected. In the future, this will be fixed by tagging such addresses.

Last updated