Token Metrics

Paresh Masani

Essentials we take into consideration when evaluating technology of a project.

Technology Review Guide

Architecture should clearly represent how it is protected against possible security attacks.

Attack Resistance

We look for attention to details and a solid architecture that can be easily explained in an unambiguous way.

Complexity

The technology architecture must be explained in a concise, accurate, and modular way so it’s easy and quick to understand.

Documentation

We make a decision based on the overall quality of the architecture and technology used to implement the idea.

Overall Architecture

We look for how well the overall technology concept is explained in the whitepaper.

Whitepaper

Architecture

If we think the project could have used a better programming language then we take off a point from this section.

Better Programming Language

We look for code comments made at the file level or function level.

Code Comments

We expect minimum activity being made on Github or open-source code repositories each month.

Code Commits Per Month

We check the project’s Github or open-source repository number of lines of source-code.

Lines of Code

It’s very important for the project to follow well-known tools and best practices for maintenance.

Maintainability Index

The project that we review must be open source otherwise there’s no way we can evaluate the code quality and other important factors.

Open Source

We are very careful to analyze that the project uses the most suitable programming language to implement their idea.

Programming Language

We check the quality of code in terms of programming languages used, overall technical architecture and design patterns used, etc.

Quality of Code

The overall test coverage is important to make sure the project is spending a good amount of time checking the quality of their source-code.

Test Coverage

Code Quality

A valid Blockchain use-case for the project being reviewed is absolutely mandatory.

Blockchain Use-Case

We must see the feasibility of the promises that the project makes.

Feasibility

The whitepaper must be concise, clear, and must specify related business and technology concept accurately and unambiguously.

Professional Whitepaper

The official document of the project should clearly specify how the underlying technology addresses the security attacks.

Security Attacks

We must clearly see a viable use-case on in a project’s official documents or website.

Viability

Initial Screening

We evaluate the project’s performance based on similar existing projects in the industry.

Performance of Similar Projects

The project must concentrate on some specific and unique problems to solve. The solution must not reinvent the wheel.

Practicality

We must be able to quantify the percentage of people that will be affected by the technology innovation.

Total Addressable Audience

We must see something unique about the project e.g. consensus algorithm improvement.

Uniqueness

Innovation

We rely on the progress being made to decide whether the project will be able to deliver mainnet in the next 6 months.

Mainnet Launch

Mainnet

The number of “active” developers is very important for any project to prove their continuous development progress.

Active Developers

We are interested in the team developer's coding style to make sure they follow best practices and there are no stupid mistakes in the code.

Developer’s Coding Style

We look for each developer’s Git or any open-source activities to put them as either a junior, senior, or expert developer.

Architecture

Code Quality

Initial Screening

Innovation

Mainnet

Team

Usability for Infrastructure Projects