Anti Peer-Reviewer

Our application turns a tedious and biased academic peer-review system into a transparent process run on blockchain. Authors upload a paper with a small fee: the AI system checks basic quality and sends instant feedback. A lottery then picks qualified reviewers who have deposited a small security bond. They read the paper, give scores and comments and earn rewards for honest, timely work. If a paper passes the required score, it is permanently recorded on the network and given a digital stamp. Anyone can challenge wrongdoing, and penalties are automatically taken from dishonest reviewers.

Hardhat: How it’s made:

• Fuzzing. HardHat 3 allows us to run property-based tests directly in Solidity, meaning we can write simple test functions and have HardHat’s fuzzer automatically try thousands of random inputs. For our project, this lets us (i) simulate many stake and unstake operations to make sure our logic doesn’t allow negative balances or other mistakes; (ii) test the reward-claiming system to ensure that a user cannot claim twice or trick the system with strange review data; and (iii) check that the PaperRegistry can handle all kinds of file types or large documents without crashing. When an error is found, HardHat’s fuzzer gives us a minimal example that caused the bug, making it much easier to fix.
• Rust EVM core. These advanced tests are practical only because HardHat 3 uses a new Rust-based Ethereum engine, which runs tests much faster and with less memory than before. This means that a large set of tests that might have taken ten minutes can now finish in four minutes or less. The faster speed lets us do more security testing, try longer test runs, and check our contracts on different simulated networks, all without slowing down development.
• Build profiles. HardHat 3 introduces named build profiles like “dev”, “ci”, and “prod” that we can switch between easily. In daily development, we use the “dev” profile, which is fast and keeps debugging information turned on. In continuous integration (CI), the tests are run with optimisations and extra security checks. For production, the “prod” profile ensures that only the final, optimised version of our contracts is deployed and registered on Etherscan, so what we audit is exactly what goes live. This system keeps our workflow simple and reliable, reducing manual errors.