Bless BLESS

Roadmap On Time Delivery Rate?There is a lack of public, detailed roadmaps and delivery data.Weight 35%Insufficient data · 40 / 100

Last 4 upgrades achieved?There is a lack of recent record of protocol upgrades.Weight 30%Insufficient data · 35 / 100

Milestones to Deliver?Missing information on milestones to be disclosed for delivery.Weight 20%not specified · 35 / 100

History Extension Record?There is a lack of assessmentable historical delay data.Weight 15%Insufficient data · 40 / 100

Consensus Mechanism?Relying on the consensus mechanism of mature underlying chains, with no independent consensus of its own.Weight 30%PoSA / PoH + PoS (Dependence on underlying chains) · 75 / 100

Main network years of operation?The mainnet or token has been up for a short time and has insufficient operational history.Weight 15%Less than 1 year · 30 / 100

Recent upgrades?There is a lack of detailed information about the recent protocol upgrade.Weight 35%Insufficient data · 20 / 100

Client Diversity?As an application layer protocol, the concept of client diversity is not fully applicable.Weight 20%Not applicable / Insufficient data · 20 / 100

Deflationary Mechanism?There is a lack of clear information on deflationary mechanisms.Weight 30%No clear mechanism · 0 / 100

Inflation rate?Lack of clear token inflation rate data.Weight 25%Insufficient data · 0 / 100

Staking rate/position lock-up rate?Lack of token staking or locking data, or extremely low proportions.Weight 25%About 0% · 0 / 100

Supply Upper Limit?There is a clear cap on token supply.Weight 20%10 billion · 100 / 100

Core Development Team?The background information of core team members is public, but there is a lack of standout highlights.Weight 30%A public team with an average background · 30 / 100

Governance mechanisms?Project governance mechanisms are centralized, lacking decentralized governance.Weight 25%Centralised · 10 / 100

Financial Transparency?Lack of information on fund usage and treasury transparency.Weight 25%Insufficient data · 20 / 100

Concentration of key people?Contracts contain backdoor code, with a high concentration of critical permissions.Weight 20%High (backdoor code present) · 0 / 100

Active Address?The number of daily active addresses performed well.Weight 30%Relatively high · 85.1 / 100

Ecological chain/L2 quantity?The project has been deployed on multiple mainstream blockchains.Weight 25%Multi-chain deployment (BNB Chain, Solana, Ethereum, Cosmos) · 80 / 100

DeFi TVL?The project is not DeFi-related, and TVL data is either unsuitable or missing.Weight 25%Not applicable / Insufficient data · 20 / 100

Developer community?Developer activity is extremely low, and community activity is insufficient.Weight 20%Low activity · 0 / 100

Historical Major Failure?The contract contains backdoor code, posing a significant security risk.Weight 25%There is a risk of backdoor code · 0 / 100

Regulatory Attitude?Compliance is extremely low, and there are serious regulatory risks.Weight 30%Unfriendly · 0 / 100

Sec Attitude?There are backdoor codes and permission leaks, and the SEC has taken an unfriendly stance.Weight 30%Unfriendly · 0 / 100

Client Bug Frequency?Lack of data on client bug frequency, but overall security risks are high.Weight 15%Insufficient data · 0 / 100