Technology Review Guide | Token Metrics Help Center

Architecture

Attack Resistance

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

Written by Paresh Masani
Updated over a week ago

Complexity

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

Written by Paresh Masani
Updated over a week ago

Documentation

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

Written by Paresh Masani
Updated over a week ago

Overall Architecture

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

Written by Paresh Masani
Updated over a week ago

Whitepaper

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

Written by Paresh Masani
Updated over a week ago

Code Quality

Better Programming Language

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

Written by Paresh Masani
Updated over a week ago

Code Comments

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

Written by Paresh Masani
Updated over a week ago

Code Commits Per Month

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

Written by Paresh Masani
Updated over a week ago

Lines of Code

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

Written by Paresh Masani
Updated over a week ago

Maintainability Index

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

Written by Paresh Masani
Updated over a week ago

Open Source

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

Written by Paresh Masani
Updated over a week ago

Programming Language

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

Written by Paresh Masani
Updated over a week ago

Quality of Code

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

Written by Paresh Masani
Updated over a week ago

Test Coverage

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.

Written by Paresh Masani
Updated over a week ago

Initial Screening

Blockchain Use-Case

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

Written by Paresh Masani
Updated over a week ago

Feasibility

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

Written by Paresh Masani
Updated over a week ago

Professional Whitepaper

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

Written by Paresh Masani
Updated over a week ago

Security Attacks

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

Written by Paresh Masani
Updated over a week ago

Viability

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

Written by Paresh Masani
Updated over a week ago

Innovation

Performance of Similar Projects

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

Written by Paresh Masani
Updated over a week ago

Practicality

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

Written by Paresh Masani
Updated over a week ago

Total Addressable Audience

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

Written by Paresh Masani
Updated over a week ago

Uniqueness

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

Written by Paresh Masani
Updated over a week ago

Mainnet

Mainnet Launch

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

Written by Paresh Masani
Updated over a week ago

Team

Active Developers

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

Written by Paresh Masani
Updated over a week ago

Developer’s Coding Style

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.

Written by Paresh Masani
Updated over a week ago

Developer’s Open Source History

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

Written by Paresh Masani
Updated over a week ago

Usability for Infrastructure Projects

Ease of Use

The project must be easy to use for its intended audience.

Written by Paresh Masani
Updated over a week ago