Eden Network is a protocol designed to minimize the negative externalities of Miner/Maximally Extractable Value (MEV) on the Ethereum ecosystem. The protocol offers three related products – Eden RPC, Eden Relay, and Eden Bundles – that enable users to protect their transactions from malicious MEV attacks and help validators maximize their revenue. Eden’s native token is EDEN, which is rewarded to stakers and network users.
The project scores high in innovation due to the way it is designed as a set of associated products that can benefit various participants in the Ethereum ecosystem, including normal users, validators, block builders, MEV searchers, and traders.
Eden Network‘s architecture is well-documented, and its different components are explained in detail, making it easy to understand how they complement each other and how they can be integrated with the existing infrastructure. As a result, the project scores well in architecture.
The code quality is high, with well-commented code, good test coverage, and outstanding maintainability index. The project is also actively maintained on GitHub.
The project is available for use on mainnet since 2021 and is very easy to use for end-users.
The project is designed to be easy to use for various participants in the Ethereum ecosystem, including normal users, validators, block builders, MEV searchers, and traders.
On average, 5+ developers are building each part of the project with senior experience and a solid coding style.
Eden Network is a well-designed protocol that offers various benefits to users in the Ethereum ecosystem. Its architecture is easy to understand and integrate, while the code quality is high. Its different components are designed to benefit different participants in the ecosystem, making it a unique project that has a viable use case.
|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
|Innovation (Out Of 11)||9|
|How have similar projects performed?||Good||2|
|Are there too many innovations?||Regular||2|
|Percentage of crypto users that will use the project?||6% – 10%||3|
|Is the project unique?||Yes||2|
|Architecture (Out of 12)||11|
|Overall feeling after reading whitepaper?||Good||2|
|Resistance to possible attacks?||Good||2|
|Complexity of the architecture?||Easy||2|
|Time taken to understand the architecture?||20-50 minute||1|
|Overall feeling about the architecture after deeper research?||Good||4|
|Has the project been hacked?||No||0|
|Code Quality (out of 15)||13|
|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?||Good||1|
|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)||49|