I'm Building a DeFi Protocol in Public — 730 Contracts, 365 Days
My name is Yaseen. I'm a Solidity protocol engineer, and I'm doing something that most developers think is impossible.
I'm building AETHERIS — a complete, production-grade, cross-chain DeFi protocol — entirely in public. Every component, every security decision, every line of Yul assembly. Open source, MIT licensed, free for anyone to use.
730 smart contracts. 365 days. 2 components every day.
Why I'm Doing This
Most open-source Solidity repositories are one of two things:
- Tutorial code that looks clean but would get drained in production
- Abandoned projects with no coherent vision
I got tired of seeing protocols get exploited because developers copy-pasted code they didn't understand. I got tired of seeing $200M+ drained in a single transaction because nobody verified the invariants.
So I decided to build something different. Not just a contract. A complete protocol architecture — built the right way, from the foundation up, in public so anyone can learn from it.
What Makes AETHERIS Different
1. Yul-First Architecture
Every gas-critical path is written in Yul assembly — not because it's cool, but because it's necessary.
Standard reentrancy guard: 20,000 gas
AETHERIS reentrancy guard using EIP-1153 TSTORE: 100 gas
That's a 99.5% reduction. Here's what it looks like:
// Standard approach — expensive SSTORE
uint256 private _status;
modifier nonReentrant() {
require(_status != 2, "ReentrancyGuard: reentrant call");
_status = 2;
_;
_status = 1;
}
// AETHERIS approach — EIP-1153 TSTORE (Cancun+)
modifier nonReentrant() {
assembly {
// TLOAD: read transient storage — costs 100 gas vs 2100 for SLOAD
if tload(REENTRANCY_SLOT) {
mstore(0x00, 0xab143c06) // ReentrantCall() selector
revert(0x00, 0x04)
}
// TSTORE: write transient storage — costs 100 gas vs 20000 for SSTORE
tstore(REENTRANCY_SLOT, 1)
}
_;
assembly {
tstore(REENTRANCY_SLOT, 0) // TSTORE: clear guard after execution
}
}
Every opcode has a comment. Every gas number is real.
2. Foundry Invariant Tests
Every contract ships with mathematical proofs that critical properties cannot be violated — no matter what input an attacker provides.
contract AETHERISGuardInvariants is Test {
// Invariant: reentrancy slot must always be 0 after transaction completes
function invariant_reentrancySlotAlwaysCleared() public {
assertEq(target.getReentrancyStatus(), 0);
}
// Fuzz: guard holds for any caller, any amount, any sequence
function testFuzz_noReentrantCall(address caller, uint256 amount) public {
amount = bound(amount, 1, type(uint96).max);
vm.prank(caller);
// Prove: concurrent calls always revert
vm.expectRevert();
target.reentrantAttack(amount);
}
}
This isn't just security theater. This is the same level of verification that Tier-1 audit firms charge $100k+ to perform.
3. Real DeFi Hack Analysis
Before every component is published, the system analyzes the latest real exploit from DefiLlama's hacks database. The contract's security section directly addresses whether it's vulnerable to that specific attack pattern.
When a protocol gets drained, AETHERIS publishes the fix within 24 hours.
The Architecture
AETHERIS is being built in 7 phases:
| Phase | What We're Building |
|---|---|
| Phase 1: Invisible Shield | MEV protection, circuit breakers, flash loan detection |
| Phase 2: Yul Optimizer | Assembly-level gas optimization primitives |
| Phase 3: Intent Engine | User intent processing, solver auctions |
| Phase 4: ZK Privacy Layer | Zero-knowledge proof integration |
| Phase 5: Cross-Chain | LayerZero V2, atomic swaps |
| Phase 6: Revenue Engine | Fee capture, protocol-owned liquidity |
| Phase 7: Advanced Primitives | ERC4626, concentrated liquidity, arbitrage |
Each phase builds on the previous one. This isn't a random collection of contracts — it's a coherent protocol architecture.
What's Been Built So Far
Component #1: ERC20 Staking Token
Component #2: DeFi Lending Protocol
Component #3: Liquidity Pool Optimization
Component #4: Flash Loan Attack Detector
Every component is:
- Solidity ^0.8.24 (Cancun-ready)
- Full NatSpec documentation
- OpenZeppelin security primitives
- Yul assembly on hot paths
- Foundry invariant tests
- MIT Licensed
Follow the Build
I publish 2 components every day at 12PM and 8PM Eastern.
GitHub: github.com/yaseen98bit/crypto-opensource
If you're a Solidity developer, this is the reference implementation you've been looking for. Every pattern is production-grade. Every security decision is explained. Every gas optimization is measured.
Star the repo if you want to follow along. I'll be here every day for the next 361 days.
— Yaseen | Protocol Architect | AETHERIS
Building in public means building with accountability. Every component I publish is one I would stake real funds on. That's the standard I hold myself to.
Top comments (0)