Security
Security-critical design notes across the stack: threat models, hardening, secure defaults, and resilience under active adversaries.
Best starting points
The KelpDAO Exploit Was Not a Bug
Incident memo (April 2026): the 116,500 rsETH release via LayerZero EndpointV2 was a semantic guard failure. Signatures are not truth unless they bind to a unique, finalized source-chain debit.
Termination Is a Security Boundary: HotStuff Under UC, Delay Attacks, and the Uncomfortable Gap to Rust
Paper note (March 2026): a UC-style termination proof for HotStuff, the real invariant it relies on, and what changes when you ship it as a low-level Rust system under adversarial latency.
Designing for Catastrophic Failure: Compartmentalization and Recovery
Spec-driven research note (December 2024): Designing for Catastrophic Failure: Compartmentalization and Recovery.
ZKP Systems Engineering: Provers, Verifiers, and Operational Cost
Threat-model-first analysis (November 2024): ZKP Systems Engineering: Provers, Verifiers, and Operational Cost.
Formal Verification of Crypto Protocols: Models, Gaps, and Pain
Spec-driven research note (October 2024): Formal Verification of Crypto Protocols: Models, Gaps, and Pain.
Roadmap
- Assumptions/non-goals made explicit
- Attack surface enumeration + mitigations
- Failure containment + blast radius
- Monitoring + incident response as part of the spec