Runtime Environment and Smart Contract Security Modeling

This blog post compares EVM and NEAR runtime models and demonstrates how asynchronous calls and storage staking on NEAR change smart-contract security. It describes reentrancy variants under NEAR's asynchronous callbacks, explains the Million Small Deposits denial-of-service risk, and introduces an "insolvency attack" where incorrect storage-fee accounting lets an attacker drain funds (notably impacting liquid staking contracts and bridges). The post outlines example flows and mitigation directions (e.g., mutexes, correct storage accounting, NEP-145).