Why we chose isolated markets over pooled lending for Zendarox Vault
Pooled lending optimizes capital efficiency. Isolated markets optimize survivability when one asset blows up. Here is the trade-off we made for v0.4.
← Back to home
Engineering notes
From the protocol bench
Architecture decisions, simulation results, and audit prep — written by the engineers shipping Zendarox Vault and client builds.
YieldRouter v0.4: routing deposits without rehypothecation risk
Vault deposit() now calls routeDeposit() with explicit pool caps. A walkthrough of the call path we wired for internal QA.
Economic simulation v2 before our August audit
How we stress ETH drawdowns, oracle delay, and mercenary LP behavior before auditors arrive — and what we changed after sim v2.
Foundry invariants we run before every client handoff
A minimal invariant suite that caught reentrancy and share-price drift on a client vault — copy the pattern, not the prose.
Building an internal protocol lab for senior reviewers
Why we built a Fastify dashboard with deposit/borrow playgrounds instead of PDFs for technical recruiting.
Liquidation bonus tuning in IsolatedMarket
Why our bonus curve changed twice in June — and the sim paths that forced the second revision.
Per-market pause vs global circuit breaker
When we pause one market and keep others live — and when the global breaker trips.
Oracle staleness bounds we document for auditors
Chainlink heartbeat vs our max staleness parameter — and what breaks when they diverge.
ERC-4626 patterns we reuse on client vault builds
Arc Yield and Zendarox Vault share ideas but not code — what we standardize when embedding with client teams.
What goes in our August audit packet for Zendarox Vault
Scope doc, known issues list, invariant list, and sim scenarios — the package auditors actually use.
Designing the borrow health API for the protocol lab
How /v1/play/borrow mirrors on-chain health factors without running a fork per request.
Modeling mercenary LP behavior before client TGE
Relay Labs engagement — how we stress emission schedules when LPs leave after incentives drop.
Foundry CI we run on every client contract PR
Fuzz, invariants, slither, and gas snapshots — the pipeline before code reaches audit.
No articles match your search.