Runtime Assertions New Paradigm for Customized Contract Security
summary
Proposal introduces concurrent runtime assertions that run alongside a modified EVM in a parallel co-processor so read‑only invariants (written in Solidity) execute after a transaction and can pass or revert to mark the transaction invalid. Assertions trigger on storage slot changes, function calls or balance updates, use extended pre‑compiles to inspect call traces and set breakpoints, and claim to preserve throughput by parallel validation while removing gas pressure from core business logic.
AI-written summary · about
related talks
01h 04mContracts for C++
16mPreventing Hacks with Security Rules Written in Solidity
01h 13mHardware-Software Contracts for High Assurance with Applications to Side-Channel Security
21mPractical Verification Of Smart Contracts Using Memory Splitting
20mSolidity's most common security pitfalls and its best safeguards
50mTrust but Verify: Scaling Deductive Verification with Abstract Interpretation
33mBuilding Trustless Scaling Solutions: Security/Audits
43mConcurrency Abstractions for Application Security