Introduction
In an era marked by the rise of decentralized organizations and decision-making, the promise of Fractal comes as an intriguing value proposition. Fractal is not just another platform; it’s an advanced DAO framework aimed at revolutionizing the way on-chain decision-making occurs.
Innovation
Despite the vibrant landscape of web 2 products that have found their footing in centralized ecosystems, there is a gap in web 3 products offering similar utilities. While the concept of Fractal might not be groundbreaking in terms of originality, it has missed the mark slightly with its perceived value proposition. Current projections suggest that only 1% -5 % of crypto users employ this protocol.
Architecture
On the brighter side, Fractal’s architectural blueprint stands out. The design is well-conceived, providing a robust layout to safeguard contracts against potential threats. That said, one concern remains – the absence of a comprehensive audit. The importance of an audit in crypto, especially for platforms handling decentralized governance and finances, cannot be overstated.
Code Quality
Fractal emerges as a frontrunner when evaluated for code quality. Their GitHub repository indicates meticulous attention to detail, with commendable code comments, strong maintainability metrics, and extensive test coverage. The project is a labor of love, where quality has not been compromised.
Product Roadmap
The deployment of the project on the Polygon mainnet, with Fractal in a beta release, is a positive step. The platform’s compatibility with all EVM-compatible chains further expands its potential reach and usability.
Fractal Usability
A key strength of Fractal lies in its user-centric design. Tailored to cater to end users, Fractal is easy to navigate and offers a high degree of customizability, allowing entities to mold it according to their specific requirements.
Team
Behind the sophisticated design of Fractal is a dedicated team of over five developers. Their expertise is evident in their crafted products – marked by senior experience and a distinctive coding style. It’s heartening to see such dedication and skill driving the project forward.
Conclusion
Fractal, as a no-code DAO framework, offers a blend of promise and areas for improvement. While its innovation quotient could be higher, its robust architecture, stellar code quality, and usability demonstrate significant potential. With a strong team at its helm and a clear focus on user-centricity, Fractal could pave the way for more efficient, decentralized decision-making in the future.
Initial Screening | |||
Keep researching | |||
Does this project need to use blockchain technology? | Yes | ||
Can this project be realized? | Yes | ||
Is there a viable use case for this project? | Yes | ||
Is the project protected from commonly known attacks? | Yes | ||
Are there no careless errors in the whitepaper? | Yes | ||
Project Technology Score | |||
Description | Scorecard | ||
Innovation (Out Of 11) | 6 | ||
How have similar projects performed? | Medium | 1 | |
Are there too many innovations? | Regular | 2 | |
Percentage of crypto users that will use the project? | 1%-5% | 1 | |
Is the project unique? | Yes | 2 | |
Architecture (Out of 12) | 10 | ||
Overall feeling after reading whitepaper? | Medium | 1 | |
Resistance to possible attacks? | Good | 2 | |
Complexity of the architecture? | Not Too Complex | 2 | |
Time taken to understand the architecture? | 20-50 min | 1 | |
Overall feeling about the architecture after deeper research? | Good | 4 | |
Has the project been hacked ? | No | 0 | |
Code Quality (out of 15) | 14 | ||
Is the project open source? | Yes | 2 | |
Does the project use good code like C,C++, Rust, Erlang, Ruby, etc? | Yes | 2 | |
Could the project use better programming languages? | No | 0 | |
Github number of lines? | More than 10K | 1 | |
Github commits per month? | More than 10 | 2 | |
What is the quality of the code? | Good | 2 | |
How well is the code commented? | Outstanding | 2 | |
Overall quality of the test coverage? | Good | 1 | |
Overall quality of the maintainability index? | Outstanding | 2 | |
When Mainnet (out of 5) | 5 | ||
When does the mainnet come out? | Mainnet Ready | 5 | |
Usability for Infrastructure Projects (out of 5) | 5 | ||
Is it easy to use for the end customer? | Yes | 5 | |
Team (out of 7) | 6 | ||
Number of active developers? | 5+ | 2 | |
Developers average Git Background? | Senior | 2 | |
Developers coding style? | Solid | 2 | |
Total Score (out of 55) | 46 | ||
Percentage Score | |||
Innovation | 10.91% | ||
Architecture | 18.18% | ||
Code Quality | 25.45% | ||
Mainnet | 9.09% | ||
Usability | 9.09% | ||
Team | 10.91% | ||
Total | 83.64% |